[PATCH 3/5] md/raid5: change disk limits
From: Shaohua Li <hidden>
Date: 2017-02-07 16:56:00
Subsystem:
software raid (multiple disks) support, the rest · Maintainers:
Song Liu, Yu Kuai, Linus Torvalds
From: Shaohua Li <hidden>
Date: 2017-02-07 16:56:00
Subsystem:
software raid (multiple disks) support, the rest · Maintainers:
Song Liu, Yu Kuai, Linus Torvalds
Now we are using atomic_t to track stripes for a bio, the original limit (because of 16-bits data for the tracking) doesn't apply any more. Signed-off-by: Shaohua Li <redacted> --- drivers/md/raid5.c | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index fd3e5ce..467ad4f 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c@@ -7255,13 +7255,8 @@ static int raid5_run(struct mddev *mddev) mddev->queue->limits.discard_alignment = stripe; mddev->queue->limits.discard_granularity = stripe; - /* - * We use 16-bit counter of active stripes in bi_phys_segments - * (minus one for over-loaded initialization) - */ - blk_queue_max_hw_sectors(mddev->queue, 0xfffe * STRIPE_SECTORS); - blk_queue_max_discard_sectors(mddev->queue, - 0xfffe * STRIPE_SECTORS); + blk_queue_max_hw_sectors(mddev->queue, BLK_DEF_MAX_SECTORS); + blk_queue_max_discard_sectors(mddev->queue, UINT_MAX); /* * unaligned part of discard request will be ignored, so can't
--
2.9.3