From: "Thomas Hellström (VMware)" <thomas_os@shipmail.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: dma api errors with swiotlb
Date: Wed, 4 Sep 2019 15:02:14 +0200 [thread overview]
Message-ID: <a78c4100-4f93-d96d-60d1-d965a7769fca@shipmail.org> (raw)
In-Reply-To: <20190904125538.GA30177@infradead.org>
On 9/4/19 2:55 PM, Christoph Hellwig wrote:
> On Wed, Sep 04, 2019 at 02:54:26PM +0200, Thomas Hellström (VMware) wrote:
>> On 9/4/19 2:17 PM, Christoph Hellwig wrote:
>>> A call to dma_max_mapping_size() to limit the maximum I/O size solves
>>> that problem. With the latest kernel that should actually be done
>>> automatically by the SCSI midlayer for you.
>> Hmm, OK. I guess with a sufficient queue depth and many mappings waiting for
>> DMA completion, the SWIOTLB may fill up anyway...
>>
>> I'll see if I can come up with something.
> You are supposed to return SCSI_MLQUEUE_HOST_BUSY in that case,
> which means that the kernel won't send more commands until another
> one completed.
It looks like it does that, although when we send it, the SWIOTLB error
has already occured and been printed out, and then the sequence starts
again.
Seems like the most effective way to stop it is to decrease the queue depth.
/Thomas
next prev parent reply other threads:[~2019-09-04 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 7:59 dma api errors with swiotlb Thomas Hellström (VMware)
2019-09-04 12:17 ` Christoph Hellwig
2019-09-04 12:54 ` Thomas Hellström (VMware)
2019-09-04 12:55 ` Christoph Hellwig
2019-09-04 13:02 ` Thomas Hellström (VMware) [this message]
2019-09-04 13:16 ` Christoph Hellwig
2019-09-04 13:21 ` Thomas Hellström (VMware)
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=a78c4100-4f93-d96d-60d1-d965a7769fca@shipmail.org \
--to=thomas_os@shipmail.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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