Konrad Rzeszutek Wilk wrote: > Hey Albert, > > I've been doing some posting in this area to split the physical / bus > address translation so that multiple platforms can utilize it. I was > wondering if it makes sense to utilize some of those concepts (ie, extend it > for DMA coherency) for your code: > > https://lists.linux-foundation.org/pipermail/iommu/2010-February/002066.html > > And here is the git tree that goes on top of those patches: > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb-2.6.git > xen-swiotlb-0.5 >
Hi Konrad, Thanks for your comments. In my case, I'd like to re-use as much code from swiotlb as possible. Adding a few function calls at strategic spots (which are optimized out for cache coherent platforms) to maintain cache coherency is currently enough for me if that's acceptable. A more general approach would involve making swiotlb_bounce() platform-dependent (or at least the actual code for copying the buffers), and re-implementing map_page, sync_single and map_sg at the platform DMA code again. I've whipped through your patches. If I undestood them, you make available a kind of swiotlb "library" core on top of which you can build alternate swiotlb-based dma ops. Wouldn't it be a good idea to split the "library" code from the default swiotlb dma ops? A(n embedded) platform may just want the "library" code to implement its own dma ops, without having to pay for the extra default swiotlb dma ops implementation. Thanks, Albert _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
