From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Sami Farin <7atbggg02@sneakemail.com>
Cc: linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Linux 2.6.9 latencies: scheduler bug?
Date: Mon, 25 Oct 2004 22:43:54 +1000 [thread overview]
Message-ID: <417CF50A.6080702@yahoo.com.au> (raw)
In-Reply-To: <20041025120021.GA9917@m.safari.iki.fi>
Sami Farin wrote:
> On Mon, Oct 25, 2004 at 12:26:18AM +0300, Sami Farin wrote:
> ...
>
>>while that's running, "rtc_latencytest 1024" has max latencies of 253ms.
>>$BLOCKLIST has around two thousand lines.
>>http://safari.iki.fi/ip_tables_original_maxlat_253ms.png
>>from pressing sysrq+p while it was running, I guesstimated one evil spot
>>and added cond_resched() in there :)
>>http://safari.iki.fi/ip_tables_cond_resched.png
>>at 5s I started the script.
>
>
> forget this stupid ip_tables.c patch, latencies have nothing to do with
> netfilter code, but bad interaction between xmms, rtc_latencytest
> and iptables. I now get at max 3.1s (yup, 3100000us) latencies.
> http://safari.iki.fi/2.6.9-xmms-fun-1.png
> if you want to reproduce this:
> 1) run "rtc_latencytest 1024" (can't reproduce with "rtc_latencytest 512")
> 2) press play in xmms
> 3) start iptables-script
>
> xmms has to be prepared first.
> a) put it in repeat mode
> b) start playing >= 2 files (like that short testcase.mp3 from lame)
> c) remove the files while xmms is playing
> d) wait till xmms has played all of the selected files
> e) press stop [now then you press play in 2), xmms does silly infinite
> loop without delays while trying to open the songs]
>
> please give me patches to try, 3.1s is really evil 8-)
>
Don't think I've tried rtc_latency test. A quick search didn't turn
up its source code...
So... stupid question, is rtc_latencytest running with a realtime
scheduling policy?
next prev parent reply other threads:[~2004-10-25 12:45 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 [this message]
2004-10-25 12:53 ` Sami Farin
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=417CF50A.6080702@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=7atbggg02@sneakemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.