android_kernel_samsung_msm8976/crypto/async_tx
Dan Williams 0403e38277 dmaengine: add fence support
Some engines optimize operation by reading ahead in the descriptor chain
such that descriptor2 may start execution before descriptor1 completes.
If descriptor2 depends on the result from descriptor1 then a fence is
required (on descriptor2) to disable this optimization.  The async_tx
api could implicitly identify dependencies via the 'depend_tx'
parameter, but that would constrain cases where the dependency chain
only specifies a completion order rather than a data dependency.  So,
provide an ASYNC_TX_FENCE to explicitly identify data dependencies.

Signed-off-by: Dan Williams <dan.j.williams@intel.com>
2009-09-08 17:42:50 -07:00
..
async_memcpy.c dmaengine: add fence support 2009-09-08 17:42:50 -07:00
async_memset.c dmaengine: add fence support 2009-09-08 17:42:50 -07:00
async_pq.c dmaengine: add fence support 2009-09-08 17:42:50 -07:00
async_raid6_recov.c dmaengine: add fence support 2009-09-08 17:42:50 -07:00
async_tx.c async_tx: remove walk of tx->parent chain in dma_wait_for_async_tx 2009-08-29 19:09:27 -07:00
async_xor.c dmaengine: add fence support 2009-09-08 17:42:50 -07:00
Kconfig async_tx: add support for asynchronous RAID6 recovery operations 2009-08-29 19:09:27 -07:00
Makefile async_tx: raid6 recovery self test 2009-08-29 19:09:28 -07:00
raid6test.c async_tx: raid6 recovery self test 2009-08-29 19:09:28 -07:00