From: Ingo Molnar <mingo@elte.hu>
To: Karim Yaghmour <karim@opersys.com>
Cc: "Paul E. McKenney" <paulmck@us.ibm.com>,
Kristian Benoit <kbenoit@opersys.com>,
linux-kernel@vger.kernel.org, bhuey@lnxw.com, andrea@suse.de,
tglx@linutronix.de, pmarques@grupopie.com, bruce@andrew.cmu.edu,
nickpiggin@yahoo.com.au, ak@muc.de, sdietrich@mvista.com,
dwalker@mvista.com, hch@infradead.org, akpm@osdl.org,
Philippe Gerum <rpm@xenomai.org>
Subject: Re: PREEMPT_RT vs I-PIPE: the numbers, part 2
Date: Thu, 23 Jun 2005 00:41:23 +0200 [thread overview]
Message-ID: <20050622224123.GA7658@elte.hu> (raw)
In-Reply-To: <42B9D208.4080305@opersys.com>
* Karim Yaghmour <karim@opersys.com> wrote:
> > so ... give the -50-12 -RT tree a try and report back the lpptest
> > results you are getting.
>
> First things first, we want to report back that our setup is validated
> before we go onto this one. So we've modified LRTBF to do the
> busy-wait thing.
here's another bug in the way you are testing PREEMPT_RT irq latencies.
Right now you are doing this in lrtbf-0.1a/drivers/par-test.c:
if (request_irq ( PAR_TEST_IRQ,
&par_test_irq_handler,
#if CONFIG_PREEMPT_RT
SA_NODELAY,
#else //!CONFIG_PREEMPT_RT
SA_INTERRUPT,
#endif //PREEMPT_RT
you should set the SA_INTERRUPT flag in the PREEMPT_RT case too! I.e.
the relevant line above should be:
SA_NODELAY | SA_INTERRUPT,
otherwise par_test_irq_handler will run with interrupts enabled, opening
the window for other interrupts to be injected and increasing the
worst-case latency! Take a look at drivers/char/lpptest.c how to do this
properly. Also, double-check that there is no IRQ 7 thread running on
the PREEMPT_RT kernel, to make sure you are measuring irq latencies.
Ingo
next prev parent reply other threads:[~2005-06-22 22:52 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 17:13 PREEMPT_RT vs I-PIPE: the numbers, part 2 Kristian Benoit
2005-06-20 18:31 ` Bill Huey
2005-06-22 16:00 ` Karim Yaghmour
2005-06-22 19:29 ` Bill Huey
2005-06-22 20:05 ` Ingo Molnar
2005-06-22 20:39 ` Karim Yaghmour
2005-06-22 22:04 ` Ingo Molnar
2005-06-22 23:03 ` Lee Revell
2005-06-22 23:52 ` Karim Yaghmour
2005-06-22 23:38 ` Karim Yaghmour
2005-06-22 23:57 ` Andrea Arcangeli
2005-06-23 0:05 ` Daniel Walker
2005-06-23 0:48 ` Karim Yaghmour
2005-06-23 0:06 ` Ingo Molnar
2005-06-23 0:47 ` Karim Yaghmour
2005-06-23 0:55 ` Bill Huey
2005-06-23 1:09 ` Karim Yaghmour
2005-06-23 1:15 ` Bill Huey
2005-06-23 1:47 ` Karim Yaghmour
2005-06-23 0:59 ` David Lang
2005-06-23 1:22 ` Karim Yaghmour
2005-06-23 1:42 ` David Lang
2005-06-23 2:09 ` Karim Yaghmour
2005-06-23 2:15 ` David Lang
2005-06-23 1:34 ` Ingo Molnar
2005-06-23 2:02 ` Karim Yaghmour
2005-06-23 3:57 ` Lee Revell
2005-06-23 4:13 ` Karim Yaghmour
2005-06-22 20:10 ` Karim Yaghmour
2005-06-22 20:15 ` Bill Huey
2005-06-21 1:55 ` Paul E. McKenney
2005-06-21 2:29 ` Karim Yaghmour
2005-06-22 1:19 ` Paul E. McKenney
2005-06-22 15:31 ` Karim Yaghmour
2005-06-22 15:27 ` Kristian Benoit
2005-06-22 16:27 ` Paul E. McKenney
2005-06-22 17:20 ` Kristian Benoit
2005-06-22 17:34 ` Ingo Molnar
2005-06-22 17:40 ` Ingo Molnar
2005-06-22 18:12 ` Karim Yaghmour
2005-06-22 18:14 ` Ingo Molnar
2005-06-22 19:04 ` Karim Yaghmour
2005-06-22 18:50 ` Paul E. McKenney
2005-06-22 19:04 ` Ingo Molnar
2005-06-22 20:17 ` Karim Yaghmour
2005-06-22 20:22 ` Ingo Molnar
2005-06-22 21:03 ` Karim Yaghmour
2005-06-22 21:10 ` Ingo Molnar
2005-06-22 21:32 ` Karim Yaghmour
2005-06-22 22:41 ` Ingo Molnar [this message]
2005-06-22 23:02 ` Karim Yaghmour
2005-06-22 21:20 ` Paul E. McKenney
2005-06-22 19:08 ` Karim Yaghmour
2005-06-23 14:48 ` Paulo Marques
2005-06-22 17:58 ` Karim Yaghmour
2005-06-22 18:47 ` Paul E. McKenney
2005-06-22 19:16 ` Karim Yaghmour
2005-06-22 21:23 ` Paul E. McKenney
2005-06-22 17:17 ` Lee Revell
2005-06-22 17:32 ` Karim Yaghmour
2005-06-29 7:43 ` PREEMPT_RT & threading IRQ 0 Ingo Molnar
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=20050622224123.GA7658@elte.hu \
--to=mingo@elte.hu \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=bhuey@lnxw.com \
--cc=bruce@andrew.cmu.edu \
--cc=dwalker@mvista.com \
--cc=hch@infradead.org \
--cc=karim@opersys.com \
--cc=kbenoit@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=paulmck@us.ibm.com \
--cc=pmarques@grupopie.com \
--cc=rpm@xenomai.org \
--cc=sdietrich@mvista.com \
--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 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.