From: Jiri Slaby <jslaby@suse.cz>
To: Chen Bough <Haibo.Chen@freescale.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [RFC] sdhci: fix DMA leaks [was: [SHDCI] Heavy (thousands) DMA leaks]
Date: Wed, 5 Aug 2015 17:11:48 +0200 [thread overview]
Message-ID: <55C227B4.3030102@suse.cz> (raw)
In-Reply-To: <55C1F919.4080002@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On 08/05/2015, 01:52 PM, Jiri Slaby wrote:
>> Yes, I see:
>> sdhci-pci 0000:02:00.0: swiotlb buffer is full (sz: 65536 bytes)
>> after some time. The driver falls back to non-DMA transfers after that.
>> It also generates a warning about that:
>> WARNING: CPU: 0 PID: 0 at drivers/mmc/host/sdhci.c:857
>> sdhci_prepare_data+0x8ec/0x900 [sdhci]()
>
> I am attaching a debug patch and a debug log. You can see where
> 0x00000000fffb0000 and 0x00000000fffe0000 is leaked. It is when 'invalid
> cookie' error happens.
And you could see the cookie handling is totally bogus.
With this rewrite, I no longer see the problems. Could you confirm it
still does the good job with respect to performance -- the numbers you
mentioned in your commit.
Ulf, what do you think about the attached patch? (Do not look at the
commented info prints.)
thanks,
--
js
suse labs
[-- Attachment #2: fix.patch --]
[-- Type: application/mbox, Size: 6244 bytes --]
next prev parent reply other threads:[~2015-08-05 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 9:31 [SHDCI] Heavy (thousands) DMA leaks Jiri Slaby
2015-07-31 6:56 ` Chen Bough
2015-08-03 9:30 ` Chen Bough
2015-08-03 9:39 ` Jiri Slaby
2015-08-05 11:52 ` Jiri Slaby
2015-08-05 15:11 ` Jiri Slaby [this message]
2015-08-05 16:25 ` [RFC] sdhci: fix DMA leaks [was: [SHDCI] Heavy (thousands) DMA leaks] Pavel Machek
2015-08-06 7:42 ` Chen Bough
2015-08-06 9:06 ` Jiri Slaby
2015-08-06 9:17 ` Chen Bough
2015-08-24 16:26 ` Laura Abbott
2015-08-25 1:50 ` Chen Bough
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=55C227B4.3030102@suse.cz \
--to=jslaby@suse.cz \
--cc=Haibo.Chen@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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