linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Mark Salter <msalter@redhat.com>
Cc: Russell King <linux@arm.linux.org.uk>,
	Chen Peter-B29397 <B29397@freescale.com>,
	"ming.lei@canonical.com" <ming.lei@canonical.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Will Deacon <Will.Deacon@arm.com>,
	"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
	Greg KH <greg@kroah.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] usb: ehci: make HC see up-to-date qh/qtd descriptor ASAP
Date: Wed, 31 Aug 2011 17:12:48 +0100	[thread overview]
Message-ID: <4E5E5D80.6080409@arm.com> (raw)
In-Reply-To: <1314804471.2344.79.camel@deneb.redhat.com>

On 31/08/11 16:27, Mark Salter wrote:
> On Wed, 2011-08-31 at 16:21 +0100, Will Deacon wrote:
>> On Wed, Aug 31, 2011 at 02:43:33PM +0100, Mark Salter wrote:
>>> On Wed, 2011-08-31 at 09:49 +0100, Will Deacon wrote:
>>>> On Wed, Aug 31, 2011 at 01:23:47AM +0100, Chen Peter-B29397 wrote:
>>>>> One question: why this write buffer issue did not happen at UP ARM V7 platform, whose dma buffer
>>>>> also uncache, but bufferable?
>>>>
>>>> Which CPU was on this platform?
>>>
>>> Using a 3.1.0-rc4+ kernel on a Pandaboard, and running 'hdparm -t' on a
>>> usb disk drive, I see ~5.8MB/s read speed. Same kernel, but passing
>>> nosmp on the commandline, I see 20.3MB/s.
>>>
>>> Can someone explain why nosmp would make such a difference?
>>
>> Oh gawd, that's horrible. I have a feeling it's probably a separate issue
>> though, caused by:
>>
>> omap_modify_auxcoreboot0(0x200, 0xfffffdff);
>>
>> in boot_secondary for OMAP. Unfortunately I have no idea what that line is
>> doing because it ends up talking to the secure monitor.
> 
> Okay, I may poke around a bit with that to see I can get a better
> understanding.
> 
> With the patched ehci-q.c, I see no noticeable difference between smp
> and nosmp. Both get me around 23.5MB/s with my setup.

Oddly enough, this patch doesn't do anything on my Tegra setup. In both
cases, I get around 17MB/s from a crap SD card plugged in a USB reader.

This leads me to suspect that this issue is very much OMAP4 specific.
Can anyone verify this theory on other some A9 platforms?

Cheers,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2011-08-31 16:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 16:03 [PATCH] usb: ehci: make HC see up-to-date qh/qtd descriptor ASAP ming.lei-Z7WLFzj8eWMS+FvcfC7Uqw
2011-08-30 16:15 ` Alan Stern
2011-08-30 16:38 ` Mark Salter
2011-08-30 17:15   ` Alan Stern
2011-08-30 18:45     ` Mark Salter
2011-08-30 17:26   ` Will Deacon
     [not found]     ` <20110830172642.GE3464-SGELLbQ0bobZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2011-08-30 17:48       ` Greg KH
2011-08-30 17:54         ` Will Deacon
     [not found]           ` <20110830175432.GG3464-SGELLbQ0bobZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2011-08-31  0:23             ` Chen Peter-B29397
2011-08-31  8:49               ` Will Deacon
2011-08-31 12:33                 ` Chen Peter-B29397
2011-08-31 13:43                 ` Mark Salter
2011-08-31 15:21                   ` Will Deacon
2011-08-31 15:27                     ` Mark Salter
2011-08-31 16:12                       ` Marc Zyngier [this message]
2011-08-31 16:55                         ` Marc Dietrich
2011-09-01 10:34                           ` Marc Zyngier
     [not found]                             ` <4E5F5FA9.3010305-5wv7dgnIgG8@public.gmane.org>
2011-09-01 11:13                               ` Marc Dietich
2011-09-01 19:08                                 ` Stephen Warren
2011-09-02  9:50                                   ` Marc Zyngier
2011-09-02 17:07                                     ` Stephen Warren
     [not found]                                   ` <74CDBE0F657A3D45AFBB94109FB122FF04B327A383-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-09-02 11:13                                     ` Marc Dietich
2011-08-31 17:46                     ` Nicolas Pitre
2011-08-31 17:51                       ` Will Deacon
     [not found]                         ` <20110831175147.GI8777-SGELLbQ0bobZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2011-08-31 18:19                           ` Rob Herring
2011-08-31 18:35                             ` Mark Salter
2011-08-31 18:49                               ` Rob Herring
     [not found]                                 ` <4E5E8230.9060307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-08-31 18:58                                   ` Mark Salter
2011-08-31 19:35                             ` Will Deacon
2011-09-08 22:41                               ` Mark Salter
     [not found]                                 ` <1315521779.2313.29.camel-PDpCo7skNiwAicBL8TP8PQ@public.gmane.org>
2011-10-31  6:49                                   ` Pandita, Vikram
2011-08-31  0:56           ` Ming Lei
2011-09-01 23:16   ` Grant Grundler

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=4E5E5D80.6080409@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=B29397@freescale.com \
    --cc=Will.Deacon@arm.com \
    --cc=greg@kroah.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=ming.lei@canonical.com \
    --cc=msalter@redhat.com \
    --cc=stern@rowland.harvard.edu \
    /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).