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 16:11:32 +0300 [thread overview]
Message-ID: <20041025131132.GD9917@m.safari.iki.fi> (raw)
In-Reply-To: <20041025125807.GA8432@elte.hu>
On Mon, Oct 25, 2004 at 02:58:07PM +0200, Ingo Molnar wrote:
>
> * Sami Farin <7atbggg02@sneakemail.com> wrote:
>
> > 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
>
> to further debug any latencies please apply the -RT patchset
which includes also -mm1...
> and enable PREEMPT_TIMING (and LATENCY_TRACING), that enables us to tell us more
I guess those are not available as individual patches which could be
applied to 2.6.9?
Could someone with LATENCY_TRACING+PREEMPT_TIMING try to reproduce
that xmms/rtc_latencytest/iptables thing... takes only a minute.
Pretty please?
> about the latencies. You dont have to enable PREEMPT_REALTIME (the most
> experimental feature of the patchset) to measure latencies.
>
> Ingo
--
prev parent reply other threads:[~2004-10-25 13:11 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
2004-10-25 12:58 ` Ingo Molnar
2004-10-25 13:11 ` Sami Farin [this message]
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=20041025131132.GD9917@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®