]> git.baikalelectronics.ru Git - kernel.git/commit
Revert "block: remove artifical max_hw_sectors cap"
authorJeff Moyer <jmoyer@redhat.com>
Thu, 13 Aug 2015 18:57:56 +0000 (14:57 -0400)
committerJens Axboe <axboe@fb.com>
Tue, 18 Aug 2015 20:21:13 +0000 (13:21 -0700)
commit4a107c8c025b9b2c22f469857dc4e993b1d13c28
tree51526a90f372dca0811c93e0311c5b5301d094be
parent107a6c04b382ac5c71d1a7987312b4f5857a12b0
Revert "block: remove artifical max_hw_sectors cap"

This reverts commit d290c3e42458bfdb5e94ad5b83bf91dd5f01bbcc.
That commit caused performance regressions for streaming I/O
workloads on a number of different storage devices, from
SATA disks to external RAID arrays.  It also managed to
trip up some buggy firmware in at least one drive, causing
data corruption.

The next patch will bump the default max_sectors_kb value to
1280, which will accommodate a 10-data-disk stripe write
with chunk size 128k.  In the testing I've done using iozone,
fio, and aio-stress, a value of 1280 does not show a big
performance difference from 512.  This will hopefully still
help the software RAID setup that Christoph saw the original
performance gains with while still not regressing other
storage configurations.

Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
block/blk-settings.c
drivers/block/aoe/aoeblk.c
include/linux/blkdev.h