From: Lee Revell <rlrevell@joe-job.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: kus Kusche Klaus <kus@keba.com>,
linux-usb-users@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.11, USB: High latency?
Date: Wed, 30 Mar 2005 16:28:14 -0500 [thread overview]
Message-ID: <1112218094.18237.11.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0503301052070.1327-100000@ida.rowland.org>
On Wed, 2005-03-30 at 10:55 -0500, Alan Stern wrote:
> On Wed, 30 Mar 2005, kus Kusche Klaus wrote:
>
> > I'm performing realtime latency tests (for details about the hardware
> > and software, see my mail "[BUG] 2.6.11: Random SCSI/USB errors when
> > reading from USB memory stick" erlier today).
> >
> > Even when the errors described in my previous mail does not occur,
> > massive USB stick transfers cause latencies of 1 to 2 milliseconds,
> > which is way too much for realtime control systems.
> >
> > I observe these latencies on a vanilla 2.6.11 at any rtprio (even 99),
> > and on realtime-preempt-2.6.12-rc1-V0.7.41-11 at low rtprio (1). When
> > running the program on realtime-preempt-2.6.12-rc1-V0.7.41-11 with
> > rtprio 99, the latencies are gone, but using a rtprio higher than the
> > interrupt handlers is not realistic.
> >
> > Is there anything which can be done about it?
>
> The latencies are almost certainly caused by the USB host controller
> driver. I'm planning improvements to uhci-hcd which should help reduce
> the latency, but it will still be on the large side. And I won't have
> time to write the changes to the driver for several months.
>
> The best solution is to stop using uhci-hcd. Get a PCI card with an OHCI
> or EHCI (high-speed) controller. They do much more work in hardware,
> reducing the amount of time the driver needs to spend with interrupts
> disabled.
I think this is connected to a problem people have been reporting on the
Linux audio lists. With some USB chipsets, USB audio interfaces just
don't work. There are dropouts even at very high latencies. It appears
that interrupts are being disabled for many milliseconds. PREEMPT_RT
does not help the problem. We have pretty much decided it has to be the
kernel's fault. The problem should be fixable because it seems to work
on the other OS.
Maybe we can isolate it to a certain USB chipsets. I'll try to get more
info.
Lee
next prev parent reply other threads:[~2005-03-30 21:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 13:51 2.6.11, USB: High latency? kus Kusche Klaus
2005-03-30 15:55 ` Alan Stern
2005-03-30 21:28 ` Lee Revell [this message]
2005-03-31 11:30 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2005-03-30 22:57 David Brownell
2005-03-31 0:43 ` Lee Revell
2005-03-31 1:13 ` David Brownell
2005-03-31 1:21 ` Lee Revell
2005-03-31 1:32 ` David Brownell
2005-03-31 0:51 ` Lee Revell
2005-03-31 1:28 ` David Brownell
2005-03-31 1:32 ` Lee Revell
2005-03-31 1:40 ` David Brownell
2005-03-31 1:44 ` Lee Revell
2005-03-31 1:39 ` Lee Revell
2005-03-31 11:15 kus Kusche Klaus
2005-03-31 16:48 ` Alan Stern
2005-03-31 12:12 kus Kusche Klaus
2005-04-01 6:46 kus Kusche Klaus
2005-04-01 17:20 ` Alan Stern
2005-04-01 13:16 kus Kusche Klaus
2005-04-01 13:41 ` Ingo Molnar
2005-04-04 8:03 kus Kusche Klaus
2005-04-04 8:36 ` Ingo Molnar
2005-04-04 19:40 ` Alan Stern
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=1112218094.18237.11.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=kus@keba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
--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