md raid5 acceleration and async_tx
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest15 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/15 | dmaengine: add base support for the async_tx apidrivers/ drivers/ drivers/ +1 more | +439 | 2 replies | |
| 2/15 | ARM: Add drivers/dma to arch/arm/Kconfigarch/ | +2 | 0 replies | |
| 3/15 | dmaengine: add the async_tx apidrivers/ drivers/ drivers/ +8 more | +1286 | 0 replies | |
| 4/15 | md: add raid5_run_ops and support routinesdrivers/ include/ | +580 | 0 replies | |
| 5/15 | md: use raid5_run_ops for stripe cache operationsdrivers/ | +56 | 0 replies | |
| 6/15 | md: move write operations to raid5_run_opsdrivers/ | +131 | 0 replies | |
| 7/15 | md: move raid5 compute block operations to raid5_run_opsdrivers/ | +93 | 0 replies | |
| 8/15 | md: move raid5 parity checks to raid5_run_opsdrivers/ | +62 | 0 replies | |
| 9/15 | md: satisfy raid5 read requests via raid5_run_opsdrivers/ | +15 | 0 replies | |
| 10/15 | md: use async_tx and raid5_run_ops for raid5 expansion operationsdrivers/ | +36 | 0 replies | |
| 11/15 | md: move raid5 io requests to raid5_run_opsdrivers/ | +10 | 0 replies | |
| 12/15 | md: remove raid5 compute_block and compute_parity5drivers/ | +0 | 0 replies | |
| 13/15 | dmaengine: driver for the iop32x, iop33x, and iop13xx raid enginesdrivers/ drivers/ drivers/ +1 more | +1599 | 0 replies | |
| 14/15 | iop13xx: Surface the iop13xx adma units to the iop-adma driverarch/ include/ include/ | +752 | 0 replies | |
| 15/15 | iop3xx: Surface the iop3xx DMA and AAU units to the iop-adma driverarch/ arch/ arch/ +9 more | +1129 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 2.6.21-rc4 00/15] md raid5 acceleration and async_tx
The following patch set implements the async_tx api and modifies md-raid5 to issue memory copies and xor calculations asynchronously. Async_tx is an extension of the existing dmaengine interface in the kernel. Async_tx allows kernel code to utilize application specific acceleration engines when present and fall back to software routines otherwise. Further details can be found in the individual patch headers.
The implementation has been in -mm since 2.6.20-mm1 and has been released in various forms to IOP users since 2.6.18
(http://sourceforge.net/projects/xscaleiop). This release includes cleanups to the iop-adma driver. The md-raid5 patches are just rebased versions of the 2.6.20-rc5 release.
Given the release of an acceleration engine driver for another platform (440spe http://marc.info/?l=linux-raid&m=117400143317440&w=2), I feel more comfortable broaching the subject of 2.6.22 inclusion.
Regards,
Dan
Dan Williams (15):
dmaengine: add base support for the async_tx api
ARM: Add drivers/dma to arch/arm/Kconfig
dmaengine: add the async_tx api
md: add raid5_run_ops and support routines
md: use raid5_run_ops for stripe cache operations
md: move write operations to raid5_run_ops
md: move raid5 compute block operations to raid5_run_ops
md: move raid5 parity checks to raid5_run_ops
md: satisfy raid5 read requests via raid5_run_ops
md: use async_tx and raid5_run_ops for raid5 expansion operations
md: move raid5 io requests to raid5_run_ops
md: remove raid5 compute_block and compute_parity5
dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines
iop13xx: Surface the iop13xx adma units to the iop-adma driver
iop3xx: Surface the iop3xx DMA and AAU units to the iop-adma driver