aboutsummaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorNikanth Karthikesan <knikanth@suse.de>2009-09-01 22:40:15 +0200
committerJens Axboe <jens.axboe@oracle.com>2009-09-01 22:40:15 +0200
commitc295fc05789653ef24f296299df7c5f92fe74dce (patch)
treef1b14e69ba862d41baafbb30212e918e35ba626a /init
parentMerge branch 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 (diff)
downloadlinux-dev-c295fc05789653ef24f296299df7c5f92fe74dce.tar.xz
linux-dev-c295fc05789653ef24f296299df7c5f92fe74dce.zip
block: Allow changing max_sectors_kb above the default 512
The patch "block: Use accessor functions for queue limits" (ae03bf639a5027d27270123f5f6e3ee6a412781d) changed queue_max_sectors_store() to use blk_queue_max_sectors() instead of directly assigning the value. But blk_queue_max_sectors() differs a bit 1. It sets both max_sectors_kb, and max_hw_sectors_kb 2. Never allows one to change max_sectors_kb above BLK_DEF_MAX_SECTORS. If one specifies a value greater then max_hw_sectors is set to that value but max_sectors is set to BLK_DEF_MAX_SECTORS I am not sure whether blk_queue_max_sectors() should be changed, as it seems to be that way for a long time. And there may be callers dependent on that behaviour. This patch simply reverts to the older way of directly assigning the value to max_sectors as it was before. Signed-off-by: Nikanth Karthikesan <knikanth@suse.de> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions