On 2019-06-24 12:16 p.m., Jason Gunthorpe wrote: > On Mon, Jun 24, 2019 at 10:53:38AM -0600, Logan Gunthorpe wrote: >>> It is only a very narrow case where you can take shortcuts with >>> dma_addr_t, and I don't think shortcuts like are are appropriate for >>> the mainline kernel.. >> >> I don't think it's that narrow and it opens up a lot of avenues for >> system design that people are wanting to go. If your high speed data >> path can avoid the root complex and CPU, you can design a system which a >> much smaller CPU and fewer lanes directed at the CPU. > > I mean the shortcut that something generates dma_addr_t for Device A > and then passes it to Device B - that is too hacky for mainline. Oh, that's not a shortcut. It's completely invalid and not likely to work in any case. If you're mapping something you have to pass the device that the dma_addr_t is being programmed into. > Sounded like this series does generate the dma_addr for the correct > device.. This series doesn't generate any DMA addresses with dma_map(). The current p2pdma code ensures everything is behind the same root port and only uses the pci bus address. This is valid and correct, but yes it's something to expand upon. I'll be doing some work shortly to add transactions that go through the IOMMU and calls dma_map_* when appropriate. Logan
