Messages in this thread |  | | | Date | Mon, 11 Sep 2006 19:44:16 -0400 | | From | Jeff Garzik <> | | Subject | Re: [PATCH 08/19] dmaengine: enable multiple clients and operations |
| |
Dan Williams wrote: > @@ -759,8 +755,10 @@ #endif > device->common.device_memcpy_buf_to_buf = ioat_dma_memcpy_buf_to_buf; > device->common.device_memcpy_buf_to_pg = ioat_dma_memcpy_buf_to_pg; > device->common.device_memcpy_pg_to_pg = ioat_dma_memcpy_pg_to_pg; > - device->common.device_memcpy_complete = ioat_dma_is_complete; > - device->common.device_memcpy_issue_pending = ioat_dma_memcpy_issue_pending; > + device->common.device_operation_complete = ioat_dma_is_complete; > + device->common.device_xor_pgs_to_pg = dma_async_xor_pgs_to_pg_err; > + device->common.device_issue_pending = ioat_dma_memcpy_issue_pending; > + device->common.capabilities = DMA_MEMCPY;
Are we really going to add a set of hooks for each DMA engine whizbang feature?
That will get ugly when DMA engines support memcpy, xor, crc32, sha1, aes, and a dozen other transforms.
> diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h > index c94d8f1..3599472 100644 > --- a/include/linux/dmaengine.h > +++ b/include/linux/dmaengine.h > @@ -20,7 +20,7 @@ > */ > #ifndef DMAENGINE_H > #define DMAENGINE_H > - > +#include <linux/config.h> > #ifdef CONFIG_DMA_ENGINE > > #include <linux/device.h> > @@ -65,6 +65,27 @@ enum dma_status { > }; > > /** > + * enum dma_capabilities - DMA operational capabilities > + * @DMA_MEMCPY: src to dest copy > + * @DMA_XOR: src*n to dest xor > + * @DMA_DUAL_XOR: src*n to dest_diag and dest_horiz xor > + * @DMA_PQ_XOR: src*n to dest_q and dest_p gf/xor > + * @DMA_MEMCPY_CRC32C: src to dest copy and crc-32c sum > + * @DMA_SHARE: multiple clients can use this channel > + */ > +enum dma_capabilities { > + DMA_MEMCPY = 0x1, > + DMA_XOR = 0x2, > + DMA_PQ_XOR = 0x4, > + DMA_DUAL_XOR = 0x8, > + DMA_PQ_UPDATE = 0x10, > + DMA_ZERO_SUM = 0x20, > + DMA_PQ_ZERO_SUM = 0x40, > + DMA_MEMSET = 0x80, > + DMA_MEMCPY_CRC32C = 0x100,
Please use the more readable style that explicitly lists bits:
DMA_MEMCPY = (1 << 0), DMA_XOR = (1 << 1), ...
> +/** > * struct dma_chan_percpu - the per-CPU part of struct dma_chan > * @refcount: local_t used for open-coded "bigref" counting > * @memcpy_count: transaction counter > @@ -75,27 +96,32 @@ struct dma_chan_percpu { > local_t refcount; > /* stats */ > unsigned long memcpy_count; > + unsigned long xor_count; > unsigned long bytes_transferred; > + unsigned long bytes_xor;
Clearly, each operation needs to be more compartmentalized.
This just isn't scalable, when you consider all the possible transforms.
Jeff
- 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/
|  |