Dan Williams 1e55db2d6b async_tx: ensure the xor destination buffer remains dma-mapped ... When the number of source buffers for an xor operation exceeds the hardware channel maximum async_xor creates a chain of dependent operations. The result of one operation is reused as an input to the next to continue the xor calculation. The destination buffer should remain mapped for the duration of the entire chain. To provide this guarantee the code must no longer be allowed to fallback to the synchronous path as this will preclude the buffer from being unmapped, i.e. the dma-driver will potentially miss the descriptor with !DMA_COMPL_SKIP_DEST_UNMAP. Cc: Neil Brown <neilb@suse.de> Signed-off-by: Dan Williams <dan.j.williams@intel.com>		2008-07-17 17:59:55 -07:00
..
async_memcpy.c	dmaengine: ack to flags: make use of the unused bits in the 'ack' field	2008-04-17 13:25:54 -07:00
async_memset.c	async_tx: fix async_memset compile error	2008-07-08 11:57:55 -07:00
async_tx.c	async_tx: list_for_each_entry_rcu() cleanup	2008-07-17 17:59:47 -07:00
async_xor.c	async_tx: ensure the xor destination buffer remains dma-mapped	2008-07-17 17:59:55 -07:00
Kconfig	async_tx: add the async_tx api	2007-07-13 08:06:14 -07:00
Makefile	async_tx: add the async_tx api	2007-07-13 08:06:14 -07:00