>From: Williams, Dan J >Sent: Thursday, September 20, 2007 6:28 PM >To: linux-kernel@xxxxxxxxxxxxxxx; linux-raid@xxxxxxxxxxxxxxx; >neilb@xxxxxxx >Cc: akpm@xxxxxxxxxxxxxxxxxxxx; yur@xxxxxxxxxxx; >saeed.bishara@xxxxxxxxx; Nelson, Shannon >Subject: [PATCH 2.6.23-rc7 1/3] async_tx: usage documentation >and developernotes > >Signed-off-by: Dan Williams <dan.j.williams@xxxxxxxxx> >--- > > Documentation/crypto/async-tx-api.txt | 217 >+++++++++++++++++++++++++++++++++ > 1 files changed, 217 insertions(+), 0 deletions(-) Thanks, Dan. In addition to Randy's most excellent nit-picking, here are a couple more minor nits. [...] >+4.2 "My application needs finer control of hardware channels" >+This requirement seems to arise from cases where a DMA engine >driver is [...] >+dma_async_client_chan_request triggers dmaeninge to notify >the client of s/dmaeninge/dmaengine/ [...] >+5 SOURCE >+drivers/dma/dmaengine.c: offload engine channel management routines >+drivers/dma/: location for offload engine drivers >+crypto/async_tx/async_tx.c: async_tx interface to dmaengine >and common code >+crypto/async_tx/async_memcpy.c: copy offload >+crypto/async_tx/async_memset.c: memory fill offload >+crypto/async_tx/async_xor.c: xor offload Also include/linux/dmaengine.h sln -- ====================================================================== Mr. Shannon Nelson LAN Access Division, Intel Corp. Shannon.Nelson@xxxxxxxxx I don't speak for Intel (503) 712-7659 Parents can't afford to be squeamish. - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
