From: Ed Tomlinson <edt@aei.ca>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Open Source <opensource3141@yahoo.com>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: USB performance bug since kernel 2.6.13 (CRITICAL???)
Date: Fri, 13 Oct 2006 08:12:10 -0400 [thread overview]
Message-ID: <200610130812.11157.edt@aei.ca> (raw)
In-Reply-To: <1160688386.24931.95.camel@mindpipe>
On Thursday 12 October 2006 17:26, Lee Revell wrote:
> On Thu, 2006-10-12 at 13:56 -0700, Open Source wrote:
> > Yes, I am pretty sure you are right about the timing. But it shouldn't be that way. If it is, then there's a bug.
> >
> > I'm fully willing to accept there is something else I should be doing driver-wise, but it shoudn't require recompiling the stock distribution kernels. Otherwise, Linux is not competitive with Microsoft Windows in this regard!
> >
> > I'll try a recompile and report back. In the meantime, if anyone else has any ideas, please let me know!
> >
>
> Yes, I agree that it would be a bug. If it turns out to be related to
> CONFIG_HZ, ask your distro why they rolled it back from 1000 to 250Hz.
If this turns out to be tied to the HZ rate its a bug. It _should_ not be using
this timing to do this ergo bug. You may be able to bypass by using 1000Hz
but this is not a fix...
Ed Tomlinson
next prev parent reply other threads:[~2006-10-13 12:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 20:56 USB performance bug since kernel 2.6.13 (CRITICAL???) Open Source
2006-10-12 21:26 ` Lee Revell
2006-10-13 12:12 ` Ed Tomlinson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-14 16:33 Open Source
2006-10-13 23:30 Open Source
2006-10-14 0:24 ` Alan Cox
2006-10-13 19:31 Open Source
2006-10-12 20:05 Open Source
2006-10-12 20:19 ` Lee Revell
2006-10-12 19:33 Open Source
2006-10-12 19:55 ` Lee Revell
2006-10-12 19:21 Open Source
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=200610130812.11157.edt@aei.ca \
--to=edt@aei.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=opensource3141@yahoo.com \
--cc=rlrevell@joe-job.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.