From: Lucas Stach <l.stach@pengutronix.de>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: large DMA segments vs SWIOTLB
Date: Thu, 01 Aug 2019 10:35:02 +0200 [thread overview]
Message-ID: <1564648502.7267.27.camel@pengutronix.de> (raw)
In-Reply-To: <20190801072958.GA16178@lst.de>
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 size, so I guess I need to dig in to see why I'm
still getting requests larger than the SWIOTLB max segment size. Thanks
for the pointer!
Regards,
Lucas
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-08-01 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 14:40 large DMA segments vs SWIOTLB Lucas Stach
2019-08-01 7:29 ` Christoph Hellwig
2019-08-01 8:35 ` Lucas Stach [this message]
2019-08-01 14:00 ` Christoph Hellwig
2019-08-05 15:56 ` Lucas Stach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1564648502.7267.27.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox