From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] queue usb hotplug events
Date: Sat, 07 Jun 2003 19:22:23 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105501388018455@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105498661302046@msgid-missing>
Olaf Hering wrote:
> Hi,
>
> there is a hardcoded sleep 3 in the usb.agent. But this is wrong,
> because the kernel runs all hotplug events at once for a new hub. The
> result is that every event still runs in parallel, just 3 seconds later.
That "sleep" is a workaround for "uhci" and "usb-uhci" bugs:
they don't queue control transfers. No complete user mode
workaround is possible; it doesn't affect just hotplug, or
even just usbfs-based applications.
The real fix is just to get rid of it on 2.5, where "uhci-hcd"
has been fixed, rather than to keep making all USB hotplugging
be annoyingly slow.
That's why I won't merge this patch.
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-06-07 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 11:43 [PATCH] queue usb hotplug events Olaf Hering
2003-06-07 19:22 ` David Brownell [this message]
2003-06-07 19:25 ` Olaf Hering
2003-06-07 19:34 ` David Brownell
2003-06-07 19:34 ` Olaf Hering
2003-06-08 7:23 ` Olaf Hering
2003-06-08 19:10 ` David Brownell
2003-06-09 11:34 ` Olaf Hering
2003-06-09 15:25 ` Olaf Hering
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=marc-linux-hotplug-105501388018455@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).