From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] usb: ehci: fix update qtd->token in qh_append_tds
Date: Sat, 27 Aug 2011 09:07:46 -0700 [thread overview]
Message-ID: <20110827160746.GA11076@kroah.com> (raw)
In-Reply-To: <CACVXFVM_p_XPyOOgz7kbEo93SCCxPa4X_vjYGm+fUGMPSFM4EA@mail.gmail.com>
On Sat, Aug 27, 2011 at 11:33:26PM +0800, Ming Lei wrote:
> Hi,
>
> On Sat, Aug 27, 2011 at 11:13 PM, Greg KH <greg@kroah.com> wrote:
> > On Sat, Aug 27, 2011 at 10:48:35PM +0800, ming.lei at canonical.com wrote:
> >> From: Ming Lei <ming.lei@canonical.com>
> >>
> >> This patch fixs one performance bug on ARM Cortex A9 dual core platform,
> >> which has been reported on quite a few ARM machines(OMAP4, Tegra 2, snowball...),
> >> see details from link of https://bugs.launchpad.net/bugs/709245.
> >>
> >> In fact, one mb() on ARM is enough to flush L2 cache, but
> >> 'dummy->hw_token = token;' after mb() is added just for obeying
> >> correct mb() usage.
> >
> > Really? ?A mb() should not be flushing any caches, it's just a memory
> > barrier. ?Or is ARM somehow "special" in this way?
>
> As Santosh pointed out, mb on ARM will flush L2 write buffer. The
> description here is wrong.
Then this can't be accepted as-is :)
> I think the below should make the writing reach into memory on all
> ARCH after ' token = dummy->hw_token;' is executed.
>
> dummy->hw_token = token;
> mb()
> token = dummy->hw_token;
>
> The above is the idea introduced to fix the problem.
Are you sure? Have you read the documentation about memory barriers to
confirm this?
> >> The patch has been tested ok on OMAP4 panda A1 board, the performance
> >> of 'dd' over usb mass storage can be increased from 4~5MB/sec to
> >> 14~16MB/sec after applying this patch.
> >
> > That's impressive, but I don't think this is really the proper way to do
> > this...
> >
> >> Signed-off-by: Ming Lei <ming.lei@canonical.com>
> >> ---
> >> ?drivers/usb/host/ehci-q.c | ? 14 ++++++++++++++
> >> ?1 files changed, 14 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/drivers/usb/host/ehci-q.c b/drivers/usb/host/ehci-q.c
> >> index 0917e3a..65b5021 100644
> >> --- a/drivers/usb/host/ehci-q.c
> >> +++ b/drivers/usb/host/ehci-q.c
> >> @@ -1082,6 +1082,20 @@ static struct ehci_qh *qh_append_tds (
> >> ? ? ? ? ? ? ? ? ? ? ? wmb ();
> >> ? ? ? ? ? ? ? ? ? ? ? dummy->hw_token = token;
> >>
> >> + ? ? ? ? ? ? ? ? ? ? /* The mb() below is added to make sure that
> >> + ? ? ? ? ? ? ? ? ? ? ?* 'token' can be writen into qtd, so that ehci
> >> + ? ? ? ? ? ? ? ? ? ? ?* HC can see the up-to-date qtd descriptor. On
> >> + ? ? ? ? ? ? ? ? ? ? ?* some archs(at least on ARM Cortex A9 dual core),
> >> + ? ? ? ? ? ? ? ? ? ? ?* writing into coherenet memory doesn't mean the
> >> + ? ? ? ? ? ? ? ? ? ? ?* value written can reach physical memory
> >> + ? ? ? ? ? ? ? ? ? ? ?* immediately, and the value may be buffered
> >> + ? ? ? ? ? ? ? ? ? ? ?* inside L2 cache. 'dummy->hw_token = token;'
> >> + ? ? ? ? ? ? ? ? ? ? ?* after mb() is added for obeying correct mb()
> >> + ? ? ? ? ? ? ? ? ? ? ?* usage.
> >> + ? ? ? ? ? ? ? ? ? ? ?* */
> >> + ? ? ? ? ? ? ? ? ? ? mb();
> >> + ? ? ? ? ? ? ? ? ? ? token = dummy->hw_token;
> >
> > Your comment does not match the code, so something is wrong here.
>
> If you mean "L2 cache flush", I confess to the mistaken description,
> and will update it later. If you mean others, could you help to point it out?
I mean others, please read the the last 3 lines of the comment and
compare that to the code lines you added.
greg k-h
next prev parent reply other threads:[~2011-08-27 16:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 14:48 [PATCH] usb: ehci: fix update qtd->token in qh_append_tds ming.lei at canonical.com
2011-08-27 15:03 ` Santosh
2011-08-27 15:18 ` Ming Lei
2011-08-27 15:46 ` Santosh
2011-08-27 15:13 ` Greg KH
2011-08-27 15:33 ` Ming Lei
2011-08-27 16:07 ` Greg KH [this message]
2011-08-27 16:57 ` Ming Lei
2011-08-27 17:20 ` Ming Lei
2011-08-27 20:11 ` Alan Stern
2011-08-28 3:35 ` Ming Lei
2011-08-27 20:06 ` Alan Stern
2011-08-28 3:13 ` Ming Lei
2011-08-28 17:00 ` Alan Stern
2011-08-28 23:36 ` Russell King - ARM Linux
2011-08-29 1:51 ` Alan Stern
2011-08-29 8:52 ` Russell King - ARM Linux
2011-08-29 13:57 ` Alan Stern
2011-08-29 15:55 ` Ming Lei
2011-08-29 16:24 ` Mark Salter
2011-08-29 14:25 ` Ming Lei
2011-08-29 15:03 ` Alan Stern
2011-08-29 15:21 ` Ming Lei
2011-08-29 16:33 ` Alan Stern
2011-08-30 14:02 ` Ming Lei
2011-08-27 16:31 ` Sergei Shtylyov
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=20110827160746.GA11076@kroah.com \
--to=greg@kroah.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).