diff options
author | Dan Williams <dan.j.williams@intel.com> | 2009-07-14 13:40:19 -0700 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2009-08-29 19:13:12 -0700 |
commit | ac6b53b6e6acab27e4f3e2383f9ac1f0d7c6200b (patch) | |
tree | e9c67502fd32a9eea4902ea382e51eecb09f2a54 /drivers/md/dm-snap.h | |
parent | 4e7d2c0aefb77f7b24942e5af042a083be4d60bb (diff) | |
download | op-kernel-dev-ac6b53b6e6acab27e4f3e2383f9ac1f0d7c6200b.zip op-kernel-dev-ac6b53b6e6acab27e4f3e2383f9ac1f0d7c6200b.tar.gz |
md/raid6: asynchronous raid6 operations
[ Based on an original patch by Yuri Tikhonov ]
The raid_run_ops routine uses the asynchronous offload api and
the stripe_operations member of a stripe_head to carry out xor+pq+copy
operations asynchronously, outside the lock.
The operations performed by RAID-6 are the same as in the RAID-5 case
except for no support of STRIPE_OP_PREXOR operations. All the others
are supported:
STRIPE_OP_BIOFILL
- copy data into request buffers to satisfy a read request
STRIPE_OP_COMPUTE_BLK
- generate missing blocks (1 or 2) in the cache from the other blocks
STRIPE_OP_BIODRAIN
- copy data out of request buffers to satisfy a write request
STRIPE_OP_RECONSTRUCT
- recalculate parity for new data that has entered the cache
STRIPE_OP_CHECK
- verify that the parity is correct
The flow is the same as in the RAID-5 case, and reuses some routines, namely:
1/ ops_complete_postxor (renamed to ops_complete_reconstruct)
2/ ops_complete_compute (updated to set up to 2 targets uptodate)
3/ ops_run_check (renamed to ops_run_check_p for xor parity checks)
[neilb@suse.de: fixes to get it to pass mdadm regression suite]
Reviewed-by: Andre Noll <maan@systemlinux.org>
Signed-off-by: Yuri Tikhonov <yur@emcraft.com>
Signed-off-by: Ilya Yanok <yanok@emcraft.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'drivers/md/dm-snap.h')
0 files changed, 0 insertions, 0 deletions