On Tue, Aug 10, 2021 at 10:19 AM Mi, Dapeng1 <dapeng1...@intel.com> wrote: > > Hi David, > > I like this patch set and this is crucial for reducing the significant vIOMMU > performance. It looks you totally rewrite the IOMMU mapping/unmapping part > and use the dynamically allocated memory from buddy system as bounce buffer > instead of using the legacy SWIOTLB bounce buffer. As I know, some legacy > devices' DMA could not access the memory larger than 32-bit memory space and > the dynamically allocated memory address could exceed the 32-bit memory > space. Is it a problem?
My understanding is that when devices with that sort of limitation sit behind an IOMMU, the IOVA is what matters, not the physical address. The bounce bounce buffers use the same limits for IOVA allocation as the regular dma-iommu path, so compatible IOVAs will be allocated for the bounce buffers. -David > Thx, > Dapeng Mi _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
