From: Martin K. Petersen Date: Mon, 21 Sep 2009 19:46:05 +0000 (+0200) Subject: block: Do not clamp max_hw_sectors for stacking devices X-Git-Tag: v2.6.32-rc3~6^2~15 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=5dee2477df5368368b7dba810a17a3c411a1d0f0;p=profile%2Fcommon%2Fkernel-common.git block: Do not clamp max_hw_sectors for stacking devices Stacking devices do not have an inherent max_hw_sector limit. Set the default to INT_MAX so we are bounded only by capabilities of the underlying storage. Signed-off-by: Martin K. Petersen Signed-off-by: Jens Axboe --- diff --git a/block/blk-settings.c b/block/blk-settings.c index cd9b730..eaf122f 100644 --- a/block/blk-settings.c +++ b/block/blk-settings.c @@ -111,7 +111,8 @@ void blk_set_default_limits(struct queue_limits *lim) lim->max_hw_segments = MAX_HW_SEGMENTS; lim->seg_boundary_mask = BLK_SEG_BOUNDARY_MASK; lim->max_segment_size = MAX_SEGMENT_SIZE; - lim->max_sectors = lim->max_hw_sectors = BLK_DEF_MAX_SECTORS; + lim->max_sectors = BLK_DEF_MAX_SECTORS; + lim->max_hw_sectors = INT_MAX; lim->logical_block_size = lim->physical_block_size = lim->io_min = 512; lim->bounce_pfn = (unsigned long)(BLK_BOUNCE_ANY >> PAGE_SHIFT); lim->alignment_offset = 0;