From: Florian Paul Schmidt <mista.tapas@gmx.net>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: rt20 scheduling latency testcase and failure data
Date: Sat, 13 May 2006 11:20:39 +0200 [thread overview]
Message-ID: <20060513112039.41536fb5@mango.fruits> (raw)
In-Reply-To: <200605121924.53917.dvhltc@us.ibm.com>
On Fri, 12 May 2006 19:24:53 -0700
Darren Hart <dvhltc@us.ibm.com> wrote:
> The test case emulates a periodic thread that wakes up on time%PERIOD=0, so
> rather than sleeping the same amount of time each round, it checks now
> against the start of its next period and sleeps for that length of time.
> Every so often it will miss it's period, I've captured that data and included
> a few of the interesting bits below. The results are from a run with a
> period of 5ms, although I have seen them with periods as high as 17ms. The
> system was under heavy network load for some of the time, but not all.
[snip]
> I'd appreciate any feedback on the test case, and in particular suggestions on
> how I can go about determining where this lost time is being spent.
There's a multitude of ways how you can misconfigure your -rt system :)
Tell us more about your setup. Hardware? Full preemption? High
resolution timers? Priority setup? From your code i see you run at prio
98. What about the IRQ handlers? And the softirq's, too? Other software?
Flo
P.S.: I ran the test a few [20 or so] times and didn't get any failures
of the sort you see. Even with a 1ms period:
~/downloads$ ./sched_latency_lkml
-------------------------------
Scheduling Latency
-------------------------------
Running 10000 iterations with a period of 1 ms
Expected running time: 10 s
ITERATION DELAY(US) MAX_DELAY(US) FAILURES
--------- --------- ------------- --------
10000 32 47 0
Start Latency: 305 us: FAIL
Min Latency: 16 us: PASS
Avg Latency: 29 us: PASS
Max Latency: 47 us: PASS
Failed Iterations: 0
~/downloads$ uname -a
Linux mango.fruits 2.6.16-rt20 #4 PREEMPT Wed May 10 12:53:39 CEST 2006 i686 GNU/Linux
Ooops, i must admit i have the nvidia binary only kernel module loaded,
but i suppose this wouldn't make a difference for the better ;)
I got high resolution timers enabled and left the softirq threads at
their defaults.
--
Palimm Palimm!
http://tapas.affenbande.org
next prev parent reply other threads:[~2006-05-13 9:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 2:24 rt20 scheduling latency testcase and failure data Darren Hart
2006-05-13 9:20 ` Florian Paul Schmidt [this message]
2006-05-13 11:55 ` Mike Galbraith
2006-05-13 15:39 ` Steven Rostedt
2006-05-13 16:36 ` Mike Galbraith
2006-05-15 8:04 ` Ingo Molnar
2006-05-13 18:06 ` Darren Hart
2006-05-13 18:21 ` Lee Revell
2006-05-13 23:01 ` Darren Hart
2006-05-14 3:46 ` Mike Galbraith
2006-05-14 5:48 ` Mike Galbraith
2006-05-14 7:04 ` Darren Hart
2006-05-14 7:38 ` Mike Galbraith
2006-05-15 8:13 ` Ingo Molnar
2006-05-16 1:30 ` Darren Hart
2006-05-16 7:22 ` Sébastien Dugué
2006-05-18 9:14 ` Darren Hart
2006-05-18 11:24 ` Ingo Molnar
2006-05-18 8:44 ` Sébastien Dugué
2006-05-18 8:47 ` Ingo Molnar
2006-05-18 8:58 ` Sébastien Dugué
2006-05-18 8:56 ` Ingo Molnar
2006-05-18 9:18 ` Sébastien Dugué
2006-05-18 9:38 ` Darren Hart
2006-05-18 9:58 ` Sébastien Dugué
2006-05-19 5:48 ` Mike Galbraith
2006-05-19 5:58 ` Mike Galbraith
2006-05-15 5:43 ` Mike Galbraith
2006-05-15 16:52 ` Lee Revell
2006-05-15 11:20 ` Sébastien Dugué
2006-05-15 21:49 ` Darren Hart
2006-05-15 11:15 ` Sébastien Dugué
2006-05-15 14:34 ` Darren Hart
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=20060513112039.41536fb5@mango.fruits \
--to=mista.tapas@gmx.net \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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