From: Sami Farin <7atbggg02@sneakemail.com>
To: linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9 latencies: scheduler bug?
Date: Mon, 25 Oct 2004 15:53:47 +0300 [thread overview]
Message-ID: <20041025125346.GC9917@m.safari.iki.fi> (raw)
In-Reply-To: <417CF50A.6080702@yahoo.com.au>
On Mon, Oct 25, 2004 at 10:43:54PM +1000, Nick Piggin wrote:
...
> Don't think I've tried rtc_latency test. A quick search didn't turn
> up its source code...
it's in package latencytest-0.42-png.tar.gz
and homepage seems to be http://www.gardena.net/benno/linux/audio/
http://www.gardena.net/benno/linux/latencytest-0.42-png.tar.gz
code hasn't changed since 2001, it seems.
> So... stupid question, is rtc_latencytest running with a realtime
> scheduling policy?
yes, it also does mlockall().
--
next prev parent reply other threads:[~2004-10-25 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 21:26 Linux 2.6.9 latencies: 253ms in ip_tables.c:copy_entries_to_user(), 200ms in reiserfs/bitmap.c:scan_bitmap_block(), 4ms in i2c-algo-bit.c:bit_xfer() Sami Farin
2004-10-25 12:00 ` Linux 2.6.9 latencies: scheduler bug? Sami Farin
2004-10-25 12:43 ` Nick Piggin
2004-10-25 12:53 ` Sami Farin [this message]
2004-10-25 12:58 ` Ingo Molnar
2004-10-25 13:11 ` Sami Farin
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=20041025125346.GC9917@m.safari.iki.fi \
--to=7atbggg02@sneakemail.com \
--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
all inboxes | Powered by JetHome®