From: Rene Herman <rene.herman@keyaccess.nl>
To: "Lev A. Melnikovsky" <melnikovsky@mail.ru>
Cc: Alessandro Suardi <alessandro.suardi@gmail.com>,
David Brownell <david-b@pacbell.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ehci-hcd affects hda speed
Date: Tue, 15 Apr 2008 22:24:17 +0200 [thread overview]
Message-ID: <48050EF1.8050507@keyaccess.nl> (raw)
In-Reply-To: <alpine.LFD.1.10.0804152220560.6429@nev.ubzr>
On 15-04-08 21:56, Lev A. Melnikovsky wrote:
> Sorry, I had virtually no time to answer earlier. If (hopefully) someone
> is still interested, here's my feedback
Interested yes, although being no longer in posession of the hardware it's a
somewhat academic interest...
> I have repeated experiments with P3B-F and VT6212L combination (to
> improve visibility the AsyncSchedSleepTime is set to 1us):
>
> #0. Nothing is connected to USB, no ehci-hcd loaded
> hda throughput 28+-1MB/s
>
> #1. ehci-hcd loaded, still no USB peripherals
> hda throughput 28+-1 MB/s
>
> #2. Something (USB hub and FLASH drive tested) is attached
> hda throughput 15+-1 MB/s
>
> #3. All USB peripherals are removed
> hda throughput 15+-1 MB/s
>
> #4. ehci-hcd is rmmod'ed
> hda throughput 28+-1MB/s
>
> The oddest peculiarity for me is the hysteretic difference between #1 and
> #3 states. I mean experimental data (hda throughput) depends not on the
> state (hardware/loaded modules), but on the path we followed.
On the chip having inited itself at least. Yes, your results match what I
experienced.
> Interestingly enough, sampling registers (via /sys) often shows Async bit
> set of the status register in the state #3. It is always cleared in #1.
> The async file is empty in both states. I wonder, how many degrees of
> freedom does an empty schedule have? Does "empty" mean "has no incomplete
> requests" or "has no requests at all"? Just guessing...
Should leave this up to David, but as far as I'm aware "no at all".
> RH> The sleep time wasn't the core problem, so I wonder of later VIA chips do
> RH> still have the active async schedule problem...
> I don't think this is purely VIA problem. I did not _try_ to install that
> VT6212L card into newer motherboard, but my _feeling_ is that we see an
> "incompatibility" between older PCI mobo chipsets and VIA USB controller.
I very much doubt that. Can't really imagine an off-silicon reason the chip
would keep scanning the async schedule. I'm also now using a NEC controller
card in that same machine and it also shows no problems.
> Actually, taking into account superior PCI bandwidth of modern PCs (if
> compared with my old P3B-F motherboard) I am not sure we can perform a
> clean reliable test without PCI bus analyzer.
http://lkml.org/lkml/2005/5/30/259
>
> -l
>
next prev parent reply other threads:[~2008-04-15 20:21 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
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 [this message]
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=48050EF1.8050507@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox