From: Darren Hart <dvhltc@us.ibm.com>
To: "Sébastien Dugué" <sebastien.dugue@bull.net>
Cc: Ingo Molnar <mingo@elte.hu>, Lee Revell <rlrevell@joe-job.com>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Mike Galbraith <efault@gmx.de>,
Steven Rostedt <rostedt@goodmis.org>,
Florian Schmidt <mista.tapas@gmx.net>
Subject: Re: rt20 scheduling latency testcase and failure data
Date: Thu, 18 May 2006 02:38:32 -0700 [thread overview]
Message-ID: <200605180238.33044.dvhltc@us.ibm.com> (raw)
In-Reply-To: <1147942687.4996.28.camel@frecb000686>
On Thursday 18 May 2006 01:58, Sébastien Dugué wrote:
> On Thu, 2006-05-18 at 10:47 +0200, Ingo Molnar wrote:
> > * Sébastien Dugué <sebastien.dugue@bull.net> wrote:
> > > Darren,
> > >
> > > On Mon, 2006-05-15 at 18:30 -0700, Darren Hart wrote:
> > > > Following Ingo's example I have included the modified test case
> > > > (please see the original mail for librt.h) that starts the trace
> > > > before each sleep and disables it after we wake up. If we have
> > > > missed a period, we print the trace.
> > >
> > > Your test program fails (at least on my box) as the overhead of
> > > starting and stopping the trace in the 5 ms period is just too high.
> > >
> > > By moving the latency_trace_start() at the start of the thread
> > > function and latency_trace_stop() at the end, everything runs fine. I
> > > did not have any period missed even under heavy load.
> >
> > could you send us the fixed testcase?
>
> No problem, see attachment.
I found several similar problems in my original test case, please see my
earlier mail from today where I included a completely rewritten test case
with buffered output and new periodic logic.
The case attached here seems to try to print the trace without first stopping
it. I don't think that will result in the desired output. My new test case
addresses that issue as well.
I'd appreciate any feedback, thanks.
--
Darren Hart
IBM Linux Technology Center
Realtime Linux Team
Phone: 503 578 3185
T/L: 775 3185
next prev parent reply other threads:[~2006-05-18 9:38 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
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 [this message]
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=200605180238.33044.dvhltc@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mista.tapas@gmx.net \
--cc=rlrevell@joe-job.com \
--cc=rostedt@goodmis.org \
--cc=sebastien.dugue@bull.net \
--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