From: Alan Stern <stern@rowland.harvard.edu>
To: David Brownell <david-b@pacbell.net>
Cc: juanslayton@dslextreme.com, Aivils Stoss <aivils@latnet.lv>,
<jkosina@suse.cz>, lud <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@xenotime.net>,
<linuxconsole-dev@lists.sourceforge.net>,
<linux-input@vger.kernel.org>
Subject: Re: PROBLEM: USB keyboards works only 4 per PC host port
Date: Tue, 19 Aug 2008 16:04:44 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0808191603350.3391-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <681431.40736.qm@web82201.mail.mud.yahoo.com>
On Tue, 19 Aug 2008, David Brownell wrote:
> The OHCI scheduling is pretty simple and compact. I'd think it would
> be easy enough to make UHCI do the same sort of thing: track bandwidth
> assigned to 2^N frames (OHCI hardware imposes a smaller limit for N
> than UHCI hardware does), and pick the least loaded of those frames to
> use for new transfers. In ohci-q.c see balance(), periodic_{,un}link().
>
> Thing is that would involve changing how UHCI manages periodic transfers;
> assuming it hasn't changed those structures since last I looked.
Yes. That's the messy part; the scheduling itself is easy.
Alan Stern
next prev parent reply other threads:[~2008-08-19 20:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 16:40 PROBLEM: USB keyboards works only 4 per PC host port juanslayton
2008-08-19 18:21 ` Alan Stern
2008-08-19 19:12 ` David Brownell
2008-08-19 20:04 ` Alan Stern [this message]
2008-08-19 21:05 ` juanslayton
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 21:06 juanslayton
2008-08-08 6:02 Aivils Stoss
2008-08-09 10:42 ` Samuel Thibault
2008-08-10 3:08 ` Aivils Stoss
2008-08-15 1:49 ` Randy Dunlap
2008-08-18 11:12 ` Aivils Stoss
2008-08-18 15:14 ` Jiri Kosina
2008-08-18 15:14 ` Randy Dunlap
2008-08-19 9:57 ` Aivils Stoss
2008-08-19 15:03 ` Alan Stern
2008-08-19 15:19 ` Randy Dunlap
2008-08-19 15:23 ` Jiri Kosina
2008-08-19 17:55 ` Dmitry Torokhov
2008-08-20 5:40 ` Aivils Stoss
2008-08-02 6:05 Aivils Stoss
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=Pine.LNX.4.44L0.0808191603350.3391-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=aivils@latnet.lv \
--cc=david-b@pacbell.net \
--cc=jkosina@suse.cz \
--cc=juanslayton@dslextreme.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
--cc=rdunlap@xenotime.net \
/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).