diff options
| author | NeilBrown <neilb@suse.de> | 2009-06-16 10:54:07 +0400 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2009-06-16 10:54:07 +0400 |
| commit | a6b3deafe0c50e3e873e8ed5cc8abfcb25c05eff (patch) | |
| tree | 18ac1b0976a1e558316d45e50d7252ba4c14fd71 /drivers/md | |
| parent | b414579f4573b6dc8583e31b01dcffd13f49fd62 (diff) | |
| download | linux-a6b3deafe0c50e3e873e8ed5cc8abfcb25c05eff.tar.xz | |
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')
| -rw-r--r-- | drivers/md/raid0.c | 5 |
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) printk(KERN_ERR "md/raid0: non-zero chunk size required.\n"); return -EINVAL; } - printk(KERN_INFO "%s: setting max_sectors to %d, segment boundary to %d\n", - mdname(mddev), - mddev->chunk_size >> 9, - (mddev->chunk_size>>1)-1); blk_queue_max_sectors(mddev->queue, mddev->chunk_size >> 9); - blk_queue_segment_boundary(mddev->queue, (mddev->chunk_size>>1) - 1); mddev->queue->queue_lock = &mddev->queue->__queue_lock; ret = create_strip_zones(mddev); |