RE: [md-accel PATCH 00/19] md raid acceleration and the async_tx api
> Dan, I hope you will release these as a patchset against 2.6.22 when > it's out or 2.6.21. I find I have a lot more confidence in results, good > or bad, when comparing something I have run in production with just one > patchset added. There are enough other changes in an -rc to confuse the > issue, and I don't run them in production (at least not usually). > There has since been a some style cleanups and the raid5 refactor, but you can go grab the 2.6.21-iop1 patch series from SourceForge if you want to try these changes out. Use the attached series file instead of the one in the tarball. You can also wait for 2.6.22-iop1, which should be the final version of md-accel queued for the merge window. https://sourceforge.net/project/downloading.php?group_id=115074 =patches-2.6.21-iop1.tar.gz&47542009 > -- > bill davidsen <[EMAIL PROTECTED]> > CTO TMR Associates, Inc > Doing interesting things with small computers since 1979 Thank you for testing, Dan series Description: series
Re: [md-accel PATCH 00/19] md raid acceleration and the async_tx api
Dan Williams wrote: Greetings, Per Andrew's suggestion this is the md raid5 acceleration patch set updated with more thorough changelogs to lower the barrier to entry for reviewers. To get started with the code I would suggest the following order: [md-accel PATCH 01/19] dmaengine: refactor dmaengine around dma_async_tx_descriptor [md-accel PATCH 04/19] async_tx: add the async_tx api [md-accel PATCH 07/19] md: raid5_run_ops - run stripe operations outside sh->lock [md-accel PATCH 16/19] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines The patch set can be broken down into three main categories: 1/ API (async_tx: patches 1 - 4) 2/ implementation (md changes: patches 5 - 15) 3/ driver (iop-adma: patches 16 - 19) I have worked with Neil to get approval of the category 2 changes. However for the category 1 and 3 changes there was no obvious merge-path/maintainer to work through. I have thus far extrapolated Neil's comments about 2 out to 1 and 3, Jeff gave some direction on a early revision about the scalability of the API, and the patch set has picked up various fixes and suggestions from being in -mm for a few releases. Please help me ensure that this code is ready for Linus to pull for 2.6.23. git://lost.foo-projects.org/~dwillia2/git/iop md-accel-linus Dan, I hope you will release these as a patchset against 2.6.22 when it's out or 2.6.21. I find I have a lot more confidence in results, good or bad, when comparing something I have run in production with just one patchset added. There are enough other changes in an -rc to confuse the issue, and I don't run them in production (at least not usually). -- bill davidsen <[EMAIL PROTECTED]> CTO TMR Associates, Inc Doing interesting things with small computers since 1979 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [md-accel PATCH 00/19] md raid acceleration and the async_tx api
Dan Williams wrote: Greetings, Per Andrew's suggestion this is the md raid5 acceleration patch set updated with more thorough changelogs to lower the barrier to entry for reviewers. To get started with the code I would suggest the following order: [md-accel PATCH 01/19] dmaengine: refactor dmaengine around dma_async_tx_descriptor [md-accel PATCH 04/19] async_tx: add the async_tx api [md-accel PATCH 07/19] md: raid5_run_ops - run stripe operations outside sh-lock [md-accel PATCH 16/19] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines The patch set can be broken down into three main categories: 1/ API (async_tx: patches 1 - 4) 2/ implementation (md changes: patches 5 - 15) 3/ driver (iop-adma: patches 16 - 19) I have worked with Neil to get approval of the category 2 changes. However for the category 1 and 3 changes there was no obvious merge-path/maintainer to work through. I have thus far extrapolated Neil's comments about 2 out to 1 and 3, Jeff gave some direction on a early revision about the scalability of the API, and the patch set has picked up various fixes and suggestions from being in -mm for a few releases. Please help me ensure that this code is ready for Linus to pull for 2.6.23. git://lost.foo-projects.org/~dwillia2/git/iop md-accel-linus Dan, I hope you will release these as a patchset against 2.6.22 when it's out or 2.6.21. I find I have a lot more confidence in results, good or bad, when comparing something I have run in production with just one patchset added. There are enough other changes in an -rc to confuse the issue, and I don't run them in production (at least not usually). -- bill davidsen [EMAIL PROTECTED] CTO TMR Associates, Inc Doing interesting things with small computers since 1979 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [md-accel PATCH 00/19] md raid acceleration and the async_tx api
Dan, I hope you will release these as a patchset against 2.6.22 when it's out or 2.6.21. I find I have a lot more confidence in results, good or bad, when comparing something I have run in production with just one patchset added. There are enough other changes in an -rc to confuse the issue, and I don't run them in production (at least not usually). There has since been a some style cleanups and the raid5 refactor, but you can go grab the 2.6.21-iop1 patch series from SourceForge if you want to try these changes out. Use the attached series file instead of the one in the tarball. You can also wait for 2.6.22-iop1, which should be the final version of md-accel queued for the merge window. https://sourceforge.net/project/downloading.php?group_id=115074filename =patches-2.6.21-iop1.tar.gz47542009 -- bill davidsen [EMAIL PROTECTED] CTO TMR Associates, Inc Doing interesting things with small computers since 1979 Thank you for testing, Dan series Description: series
[md-accel PATCH 00/19] md raid acceleration and the async_tx api
Greetings, Per Andrew's suggestion this is the md raid5 acceleration patch set updated with more thorough changelogs to lower the barrier to entry for reviewers. To get started with the code I would suggest the following order: [md-accel PATCH 01/19] dmaengine: refactor dmaengine around dma_async_tx_descriptor [md-accel PATCH 04/19] async_tx: add the async_tx api [md-accel PATCH 07/19] md: raid5_run_ops - run stripe operations outside sh->lock [md-accel PATCH 16/19] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines The patch set can be broken down into three main categories: 1/ API (async_tx: patches 1 - 4) 2/ implementation (md changes: patches 5 - 15) 3/ driver (iop-adma: patches 16 - 19) I have worked with Neil to get approval of the category 2 changes. However for the category 1 and 3 changes there was no obvious merge-path/maintainer to work through. I have thus far extrapolated Neil's comments about 2 out to 1 and 3, Jeff gave some direction on a early revision about the scalability of the API, and the patch set has picked up various fixes and suggestions from being in -mm for a few releases. Please help me ensure that this code is ready for Linus to pull for 2.6.23. git://lost.foo-projects.org/~dwillia2/git/iop md-accel-linus Dan Williams (19): dmaengine: refactor dmaengine around dma_async_tx_descriptor dmaengine: make clients responsible for managing channels xor: make 'xor_blocks' a library routine for use with async_tx async_tx: add the async_tx api raid5: refactor handle_stripe5 and handle_stripe6 (v2) raid5: replace custom debug PRINTKs with standard pr_debug md: raid5_run_ops - run stripe operations outside sh->lock md: common infrastructure for running operations with raid5_run_ops md: handle_stripe5 - add request/completion logic for async write ops md: handle_stripe5 - add request/completion logic for async compute ops md: handle_stripe5 - add request/completion logic for async check ops md: handle_stripe5 - add request/completion logic for async read ops md: handle_stripe5 - add request/completion logic for async expand ops md: handle_stripe5 - request io processing in 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 ARM: Add drivers/dma to arch/arm/Kconfig Administrivia: This patch set contains three new patches compared to the previous release they are: [md-accel PATCH 03/19] xor: make 'xor_blocks' a library routine for use with async_tx [md-accel PATCH 05/19] raid5: refactor handle_stripe5 and handle_stripe6 (v2) [md-accel PATCH 06/19] raid5: replace custom debug PRINTKs with standard pr_debug net/core/dev.c is touched by the following: [md-accel PATCH 02/19] dmaengine: make clients responsible for managing channels - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[md-accel PATCH 00/19] md raid acceleration and the async_tx api
Greetings, Per Andrew's suggestion this is the md raid5 acceleration patch set updated with more thorough changelogs to lower the barrier to entry for reviewers. To get started with the code I would suggest the following order: [md-accel PATCH 01/19] dmaengine: refactor dmaengine around dma_async_tx_descriptor [md-accel PATCH 04/19] async_tx: add the async_tx api [md-accel PATCH 07/19] md: raid5_run_ops - run stripe operations outside sh-lock [md-accel PATCH 16/19] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines The patch set can be broken down into three main categories: 1/ API (async_tx: patches 1 - 4) 2/ implementation (md changes: patches 5 - 15) 3/ driver (iop-adma: patches 16 - 19) I have worked with Neil to get approval of the category 2 changes. However for the category 1 and 3 changes there was no obvious merge-path/maintainer to work through. I have thus far extrapolated Neil's comments about 2 out to 1 and 3, Jeff gave some direction on a early revision about the scalability of the API, and the patch set has picked up various fixes and suggestions from being in -mm for a few releases. Please help me ensure that this code is ready for Linus to pull for 2.6.23. git://lost.foo-projects.org/~dwillia2/git/iop md-accel-linus Dan Williams (19): dmaengine: refactor dmaengine around dma_async_tx_descriptor dmaengine: make clients responsible for managing channels xor: make 'xor_blocks' a library routine for use with async_tx async_tx: add the async_tx api raid5: refactor handle_stripe5 and handle_stripe6 (v2) raid5: replace custom debug PRINTKs with standard pr_debug md: raid5_run_ops - run stripe operations outside sh-lock md: common infrastructure for running operations with raid5_run_ops md: handle_stripe5 - add request/completion logic for async write ops md: handle_stripe5 - add request/completion logic for async compute ops md: handle_stripe5 - add request/completion logic for async check ops md: handle_stripe5 - add request/completion logic for async read ops md: handle_stripe5 - add request/completion logic for async expand ops md: handle_stripe5 - request io processing in 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 ARM: Add drivers/dma to arch/arm/Kconfig Administrivia: This patch set contains three new patches compared to the previous release they are: [md-accel PATCH 03/19] xor: make 'xor_blocks' a library routine for use with async_tx [md-accel PATCH 05/19] raid5: refactor handle_stripe5 and handle_stripe6 (v2) [md-accel PATCH 06/19] raid5: replace custom debug PRINTKs with standard pr_debug net/core/dev.c is touched by the following: [md-accel PATCH 02/19] dmaengine: make clients responsible for managing channels - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
