aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/md/raid0.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-06-16 02:54:07 -0400
committerNeilBrown <neilb@suse.de>2009-06-16 02:54:07 -0400
commita6b3deafe0c50e3e873e8ed5cc8abfcb25c05eff (patch)
tree18ac1b0976a1e558316d45e50d7252ba4c14fd71 /drivers/md/raid0.c
parentb414579f4573b6dc8583e31b01dcffd13f49fd62 (diff)
md: raid0: remove setting of segment boundary.
This setting doesn't seem to make sense (half the chunk size??) and shouldn't be needed. The segment boundary exported by raid0 should simply be the minimum of the segment boundary of all component devices. And we already get that right. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid0.c')
-rw-r--r--drivers/md/raid0.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/drivers/md/raid0.c b/drivers/md/raid0.c
index af0df78223b1..e2e9c1833336 100644
--- a/drivers/md/raid0.c
+++ b/drivers/md/raid0.c
@@ -261,12 +261,7 @@ static int raid0_run(mddev_t *mddev)
261 printk(KERN_ERR "md/raid0: non-zero chunk size required.\n"); 261 printk(KERN_ERR "md/raid0: non-zero chunk size required.\n");
262 return -EINVAL; 262 return -EINVAL;
263 } 263 }
264 printk(KERN_INFO "%s: setting max_sectors to %d, segment boundary to %d\n",
265 mdname(mddev),
266 mddev->chunk_size >> 9,
267 (mddev->chunk_size>>1)-1);
268 blk_queue_max_sectors(mddev->queue, mddev->chunk_size >> 9); 264 blk_queue_max_sectors(mddev->queue, mddev->chunk_size >> 9);
269 blk_queue_segment_boundary(mddev->queue, (mddev->chunk_size>>1) - 1);
270 mddev->queue->queue_lock = &mddev->queue->__queue_lock; 265 mddev->queue->queue_lock = &mddev->queue->__queue_lock;
271 266
272 ret = create_strip_zones(mddev); 267 ret = create_strip_zones(mddev);