From: Rene Herman <rene.herman@keyaccess.nl>
To: Alessandro Suardi <alessandro.suardi@gmail.com>
Cc: "Lev A. Melnikovsky" <melnikovsky@mail.ru>,
David Brownell <david-b@pacbell.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ehci-hcd affects hda speed
Date: Thu, 20 Mar 2008 12:35:43 +0100 [thread overview]
Message-ID: <47E24C0F.1070901@keyaccess.nl> (raw)
In-Reply-To: <5a4c581d0803192208w6db8f2aaj42eac883de126585@mail.gmail.com>
On 20-03-08 06:08, Alessandro Suardi wrote:
> On Thu, Mar 20, 2008 at 1:31 AM, Rene Herman <rene.herman@keyaccess.nl> wrote:
>> I do wonder -- is your hda throughput also the same before _ever_ attaching
>> anything to the EHCI controller and after? In my case, the slow down only
>> happened after switching on my external USB drive once, and would persist
>> from that time until reboot (or unloading ehci-hcd, which I kept modular for
>> exactly that reason).
>>
>> The sleep time wasn't the core problem, so I wonder of later VIA chips do
>> still have the active async schedule problem...
>>
>> Alessandro? You said there still was a difference for you between no EHCI at
>> all and EHCI after tweaking 4B as Lev showed. How much?
>
> When used setpci to tweak the setting, my hdparm -t went
> from 17 to 25MB/s on /dev/hda.
>
> With your patch applied, now after booting it says 33MB/s for
> hda and 37MB/s on hdb (and I can burn DVDs at a stable 6x
> now, while growisofs backed off to 4x in less than a minute
> before the patch).
>
> If the patch does exactly what setpci did, then perhaps I had
> other activity on hda at the moment I ran the test...
Yes, should be the exact same. It could be what I noted -- that you have the
33/37 just after booting, and a drop to 25 again after having switched
on/used a EHCI device for the first time? That would be interesting.
Rene.
next prev parent reply other threads:[~2008-03-20 11:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 22:27 ehci-hcd affects hda speed Lev A. Melnikovsky
2008-03-05 16:19 ` Rene Herman
2008-03-05 20:03 ` Alessandro Suardi
2008-03-05 21:03 ` David Brownell
2008-03-06 16:25 ` Alessandro Suardi
2008-03-06 20:10 ` Lev A. Melnikovsky
2008-03-10 10:11 ` Lev A. Melnikovsky
2008-03-15 22:46 ` Lev A. Melnikovsky
2008-03-17 16:15 ` Alessandro Suardi
2008-03-17 21:06 ` David Brownell
[not found] ` <47DC596A.4010800@keyaccess.nl>
[not found] ` <200803171400.40045.david-b@pacbell.net>
2008-03-17 23:23 ` Rene Herman
2008-03-17 23:26 ` Rene Herman
2008-03-18 0:00 ` David Brownell
2008-03-18 0:24 ` Lev A. Melnikovsky
2008-03-18 1:27 ` Rene Herman
2008-03-18 1:45 ` David Brownell
2008-03-18 1:23 ` Rene Herman
2008-03-18 1:55 ` David Brownell
2008-03-18 3:13 ` Rene Herman
2008-03-19 23:47 ` Lev A. Melnikovsky
2008-03-20 0:31 ` Rene Herman
2008-03-20 5:08 ` Alessandro Suardi
2008-03-20 11:35 ` Rene Herman [this message]
2008-03-20 21:01 ` Alessandro Suardi
2008-04-15 19:56 ` Lev A. Melnikovsky
2008-04-15 20:02 ` Oliver Neukum
2008-04-15 20:41 ` Lev A. Melnikovsky
2008-04-16 5:38 ` Oliver Neukum
2008-04-16 22:23 ` Lev A. Melnikovsky
2008-04-17 8:20 ` Oliver Neukum
2008-04-15 20:24 ` Rene Herman
2008-04-15 20:32 ` Rene Herman
2008-04-15 23:17 ` David Brownell
2008-04-16 22:44 ` Lev A. Melnikovsky
2008-03-18 22:02 ` Alessandro Suardi
2008-03-18 22:09 ` Rene Herman
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=47E24C0F.1070901@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alessandro.suardi@gmail.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=melnikovsky@mail.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.