diff options
author | Dan Williams <dan.j.williams@intel.com> | 2007-01-02 21:52:31 +0100 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2007-07-13 17:06:17 +0200 |
commit | f0a50d3754c7f1b7f05f45b1c0b35d20445316b5 (patch) | |
tree | c54b572ad4c4c9b48f887a9ecc28ec7b6166d552 /net | |
parent | md: handle_stripe5 - add request/completion logic for async read ops (diff) | |
download | linux-f0a50d3754c7f1b7f05f45b1c0b35d20445316b5.tar.xz linux-f0a50d3754c7f1b7f05f45b1c0b35d20445316b5.zip |
md: handle_stripe5 - add request/completion logic for async expand ops
When a stripe is being expanded bulk copying takes place to move the data
from the old stripe to the new. Since raid5_run_ops only operates on one
stripe at a time these bulk copies are handled in-line under the stripe
lock. In the dma offload case we poll for the completion of the operation.
After the data has been copied into the new stripe the parity needs to be
recalculated across the new disks. We reuse the existing postxor
functionality to carry out this calculation. By setting STRIPE_OP_POSTXOR
without setting STRIPE_OP_BIODRAIN the completion path in handle stripe
can differentiate expand operations from normal write operations.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Acked-By: NeilBrown <neilb@suse.de>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions