diff options
author | NeilBrown <neilb@suse.de> | 2011-09-10 17:21:17 +1000 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2011-09-10 17:21:17 +1000 |
commit | 19d5f834d6aff7efb1c9353523865c5bce869470 (patch) | |
tree | 01c18b17519df9034bbcaf126eac9d9318143a1d /drivers/md/md.c | |
parent | 94007751bb02797ba87bac7aacee2731ac2039a3 (diff) | |
download | op-kernel-dev-19d5f834d6aff7efb1c9353523865c5bce869470.zip op-kernel-dev-19d5f834d6aff7efb1c9353523865c5bce869470.tar.gz |
md/raid10: unify handling of write completion.
A write can complete at two different places:
1/ when the last member-device write completes, through
raid10_end_write_request
2/ in make_request() when we remove the initial bias from ->remaining.
These two should do exactly the same thing and the comment says they
do, but they don't.
So factor the correct code out into a function and call it in both
places. This makes the code much more similar to RAID1.
The difference is only significant if there is an error, and they
usually take a while, so it is unlikely that there will be an error
already when make_request is completing, so this is unlikely to cause
real problems.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/md.c')
0 files changed, 0 insertions, 0 deletions