Sorry, I had virtually no time to answer earlier. If (hopefully) someone is still interested, here's my feedback

On Thu, 20 Mar 2008 at 3:50am, Rene Herman wrote:

RH> I do wonder -- is your hda throughput also the same before _ever_ RH> attaching anything to the EHCI controller and after? In my case, the RH> slow down only happened after switching on my external USB drive once, RH> and would persist from that time until reboot (or unloading ehci-hcd, RH> which I kept modular for exactly that reason).I have repeated experiments with P3B-F and VT6212L combination (to improve visibility the AsyncSchedSleepTime is set to 1us):

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.

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...

RH> The sleep time wasn't the core problem, so I wonder of later VIA chips doRH> 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. 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.