Revert "md/raid5: limit request size according to implementation limits"

This reverts commit e8d7c33232e5fdfa761c3416539bc5b4acd12db5.

Now that raid5 doesn't abuse bi_phys_segments any more, we no longer
need to impose these limits.

Signed-off-by: NeilBrown <neilb@suse.com>
Signed-off-by: Shaohua Li <shli@fb.com>

diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 1c8be667e9a9e6334bf8669dd88de6ba48baa4ef..00a34faabcdfbf702d32c07f12c477923c6c5e4a 100644 (file)
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -7361,15 +7361,6 @@ static int raid5_run(struct mddev *mddev)
                        stripe = (stripe | (stripe-1)) + 1;
                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);
-
                /*
                 * unaligned part of discard request will be ignored, so can't
                 * guarantee discard_zeroes_data