From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Open Source <opensource3141@yahoo.com>
Cc: "Alan Stern" <stern@rowland.harvard.edu>,
linux-usb-devel@lists.sourceforge.net,
WolfgangMües <wolfgang@iksw-muees.de>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] USB performance bug since kernel 2.6.13 (CRITICAL???)
Date: Sat, 14 Oct 2006 00:41:44 +0100 [thread overview]
Message-ID: <1160782904.25218.93.camel@localhost.localdomain> (raw)
In-Reply-To: <20061013230240.84447.qmail@web58108.mail.re3.yahoo.com>
Ar Gwe, 2006-10-13 am 16:02 -0700, ysgrifennodd Open Source:
> clear understanding of what is causing it. As it stands it doesn't
> seem like even the experts know exactly where this
> delay is being caused.
strace should tell you precisely how long each syscall takes if you ask
it to trace things nicely. If you have code trying to wait for a tiny
time then HZ will bump the wait to be longer (kernel or user) but for
other cases all should be fine either way.
The other issues like priority and paging caused delays can generally be
dealt with by having the relevant service code running mlockall and real
time priority.
next prev parent reply other threads:[~2006-10-13 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 23:02 Open Source
2006-10-13 23:41 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 23:35 Open Source
2006-10-14 0:24 Alan Cox
2006-10-14 2:11 ` [linux-usb-devel] " Alan Stern
2006-10-13 19:31 Open Source
2006-10-13 21:08 ` [linux-usb-devel] " Alan Stern
2006-10-13 23:33 ` David Brownell
2006-10-13 17:20 Open Source
2006-10-13 18:02 ` Alan Stern
2006-10-13 20:24 ` Bob Copeland
2006-10-12 19:33 Open Source
2006-10-13 13:56 ` [linux-usb-devel] " 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=1160782904.25218.93.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=opensource3141@yahoo.com \
--cc=stern@rowland.harvard.edu \
--cc=wolfgang@iksw-muees.de \
/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
all inboxes | Powered by JetHome®