Messages in this thread | | | Date | Wed, 21 Dec 2005 10:28:05 +0300 | From | Evgeniy Polyakov <> | Subject | Re: [RFC][PATCH 1/5] I/OAT DMA support and TCP acceleration |
| |
On Tue, Dec 20, 2005 at 09:17:34PM -0800, Chris Leech (christopher.leech@intel.com) wrote: > DMA memcpy subsystem > Provides an API for offloading memory copies to DMA devices. > Along with client registration and DMA channel allocation, the main APIs are: > dma_async_memcpy_buf_to_buf() > dma_async_memcpy_buf_to_pg() > dma_async_memcpy_pg_to_pg() > dma_async_memcpy_complete()
Is here at least some locking? All dma chain/engine list manipulations seem very suspicious.
-- Evgeniy Polyakov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |