diff options
| author | Jeff Moyer <jmoyer@redhat.com> | 2015-08-13 14:57:57 -0400 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2015-08-18 13:21:15 -0700 |
| commit | d2be537c3ba3568acd79cd178327b842e60d035e (patch) | |
| tree | 56642354abf2b2a624615d01cabda62f5cdf7dba | |
| parent | 30e2bc08b2bb7c069246feee78f7ed4006e130fe (diff) | |
| download | linux-d2be537c3ba3568acd79cd178327b842e60d035e.tar.bz2 | |
block: bump BLK_DEF_MAX_SECTORS to 2560
A value of 2560 (1280k) will accommodate a 10-data-disk stripe
write with chunk size 128k. In the testing I've done using
iozone, fio, and aio-stress across a number of different storage
devices, a value of 1280 does not show a big performance
difference from 512, but will hopefully help software RAID
setups using SATA disks, as reported by Christoph.
NOTE: drivers/block/aoe/aoeblk.c sets its own max_hw_sectors_kb to
BLK_DEF_MAX_SECTORS. So, this patch essentially changes aeoblk to
Use a larger maximum sector size, and I did not test this.
Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
| -rw-r--r-- | include/linux/blkdev.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h index 9f1e3f8eeed7..e427debc7008 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -1132,7 +1132,7 @@ extern int blk_verify_command(unsigned char *cmd, fmode_t has_write_perm); enum blk_default_limits { BLK_MAX_SEGMENTS = 128, BLK_SAFE_MAX_SECTORS = 255, - BLK_DEF_MAX_SECTORS = 1024, + BLK_DEF_MAX_SECTORS = 2560, BLK_MAX_SEGMENT_SIZE = 65536, BLK_SEG_BOUNDARY_MASK = 0xFFFFFFFFUL, }; |