public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11, USB: High latency?
Date: Wed, 30 Mar 2005 14:57:35 -0800	[thread overview]
Message-ID: <200503301457.35464.david-b@pacbell.net> (raw)

Quoth kus@keba.com:
> 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 couldn't find that previous email in the MARC archives.

Regardless, you'd have to provide a small bit of information about
your hardware configuration.  What device speed:  full or high?
What controller:  EHCI, OHCI, UHCI, something else?  Which driver
for the stick:  usb-storage, or ub?  What else was using memory
and PCI bandwidth at the time?  SMP?


Quoth rlevell@joe-job.com:
> 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.  

Well, I'd not yet expect USB audio to work over EHCI quite yet,
though one of the patches Greg just posted should help some of
the issues with full speed iso through USB 2.0 hubs.  (At least
for OUT transfers as to speakers.)

You might consider reporting such issues on the Linux-USB list.
It's been ages since anyone reported such a bug with the OHCI
or UHCI drivers ... probably why folk have assumed there are
no problems there.


Something to consider specifically with audio.  That uses the
isochronous transfer mode, reserving USB bandwidth.  But I've
certainly seen systems with PCI busses that are severely clogged,
so that the USB controllers have a hard time accessing main
memory.  Even a perfectly functional USB stack will have a hard
time with such hardware!

- Dave

             reply	other threads:[~2005-03-30 22:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 22:57 David Brownell [this message]
2005-03-31  0:43 ` 2.6.11, USB: High latency? 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
  -- strict thread matches above, loose matches on Subject: below --
2005-04-04  8:03 kus Kusche Klaus
2005-04-04  8:36 ` Ingo Molnar
2005-04-04 19:40 ` Alan Stern
2005-04-01 13:16 kus Kusche Klaus
2005-04-01 13:41 ` Ingo Molnar
2005-04-01  6:46 kus Kusche Klaus
2005-04-01 17:20 ` Alan Stern
2005-03-31 12:12 kus Kusche Klaus
2005-03-31 11:15 kus Kusche Klaus
2005-03-31 16:48 ` Alan Stern
2005-03-30 13:51 kus Kusche Klaus
2005-03-30 15:55 ` Alan Stern
2005-03-30 21:28   ` Lee Revell
2005-03-31 11:30 ` Ingo Molnar

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=200503301457.35464.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    /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