Re: large DMA segments vs SWIOTLB

Hi Christoph, Am Donnerstag, den 01.08.2019, 16:00 +0200 schrieb Christoph Hellwig: > On Thu, Aug 01, 2019 at 10:35:02AM +0200, Lucas Stach wrote: > > Hi Christoph, > > > > Am Donnerstag, den 01.08.2019, 09:29 +0200 schrieb Christoph Hellwig: > > > Hi Lukas, > > > > > > have you tried the latest

Re: large DMA segments vs SWIOTLB

On Thu, Aug 01, 2019 at 10:35:02AM +0200, Lucas Stach wrote: > Hi Christoph, > > Am Donnerstag, den 01.08.2019, 09:29 +0200 schrieb Christoph Hellwig: > > Hi Lukas, > > > > have you tried the latest 5.3-rc kernel, where we limited the NVMe > > I/O size based on the swiotlb buffer size? > > Yes,

Re: large DMA segments vs SWIOTLB

Hi Christoph, Am Donnerstag, den 01.08.2019, 09:29 +0200 schrieb Christoph Hellwig: > Hi Lukas, > > have you tried the latest 5.3-rc kernel, where we limited the NVMe > I/O size based on the swiotlb buffer size? Yes, the issue was reproduced on 5.3-rc2. I now see your commit limiting the request

Re: large DMA segments vs SWIOTLB

Hi Lukas, have you tried the latest 5.3-rc kernel, where we limited the NVMe I/O size based on the swiotlb buffer size? ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu

large DMA segments vs SWIOTLB

Hi all, I'm currently looking at an issue with an NVMe device, which isn't working properly under some specific conditions. The issue comes down to my platform having DMA addressing restrictions, with only 3 of the total 4GiB of RAM being device addressable, which means a bunch of DMA mappings ar