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>
This commit is contained in:
parent
b414579f45
commit
a6b3deafe0
|
@ -261,12 +261,7 @@ static int raid0_run(mddev_t *mddev)
|
||||||
printk(KERN_ERR "md/raid0: non-zero chunk size required.\n");
|
printk(KERN_ERR "md/raid0: non-zero chunk size required.\n");
|
||||||
return -EINVAL;
|
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_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;
|
mddev->queue->queue_lock = &mddev->queue->__queue_lock;
|
||||||
|
|
||||||
ret = create_strip_zones(mddev);
|
ret = create_strip_zones(mddev);
|
||||||
|
|
Loading…
Reference in New Issue