summaryrefslogtreecommitdiffstats
path: root/drivers/bcma
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2012-03-19 12:46:39 +1100
committerNeilBrown <neilb@suse.de>2012-03-19 12:46:39 +1100
commit6b740b8d79252f13bcb7e5d3c1d43157e78a81e7 (patch)
tree4b99f8fb395e7a205a85766d1bd241dce39c4337 /drivers/bcma
parent050b66152f87c79e8d66aed0e7996f9336462d5f (diff)
downloadlinux-6b740b8d79252f13bcb7e5d3c1d43157e78a81e7.tar.gz
linux-6b740b8d79252f13bcb7e5d3c1d43157e78a81e7.tar.bz2
linux-6b740b8d79252f13bcb7e5d3c1d43157e78a81e7.zip
md/raid1: handle merge_bvec_fn in member devices.
Currently we don't honour merge_bvec_fn in member devices so if there is one, we force all requests to be single-page at most. This is not ideal. So create a raid1 merge_bvec_fn to check that function in children as well. This introduces a small problem. There is no locking around calls the ->merge_bvec_fn and subsequent calls to ->make_request. So a device added between these could end up getting a request which violates its merge_bvec_fn. Currently the best we can do is synchronize_sched(). This will work providing no preemption happens. If there is is preemption, we just have to hope that new devices are largely consistent with old devices. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/bcma')
0 files changed, 0 insertions, 0 deletions