aha/crypto/async_tx
Dan Williams 6f49a57aa5 dmaengine: up-level reference counting to the module level
Simply, if a client wants any dmaengine channel then prevent all dmaengine
modules from being removed.  Once the clients are done re-enable module
removal.

Why?, beyond reducing complication:
1/ Tracking reference counts per-transaction in an efficient manner, as
   is currently done, requires a complicated scheme to avoid cache-line
   bouncing effects.
2/ Per-transaction ref-counting gives the false impression that a
   dma-driver can be gracefully removed ahead of its user (net, md, or
   dma-slave)
3/ None of the in-tree dma-drivers talk to hot pluggable hardware, but
   if such an engine were built one day we still would not need to notify
   clients of remove events.  The driver can simply return NULL to a
   ->prep() request, something that is much easier for a client to handle.

Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Maciej Sosnowski <maciej.sosnowski@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
2009-01-06 11:38:14 -07:00
..
async_memcpy.c async_tx: remove depend_tx from async_tx_sync_epilog 2008-07-17 17:59:55 -07:00
async_memset.c async_tx: remove depend_tx from async_tx_sync_epilog 2008-07-17 17:59:55 -07:00
async_tx.c dmaengine: up-level reference counting to the module level 2009-01-06 11:38:14 -07:00
async_xor.c async_xor: dma_map destination DMA_BIDIRECTIONAL 2008-12-08 13:46:00 -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