From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: Bill Huey <bhuey@lnxw.com>, Kristian Benoit <kbenoit@opersys.com>,
linux-kernel@vger.kernel.org, andrea@suse.de, tglx@linutronix.de,
karim@opersys.com, 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,
rpm@xenomai.org
Subject: Re: PREEMPT_RT and I-PIPE: the numbers, take 3
Date: Thu, 30 Jun 2005 18:17:26 +0200 [thread overview]
Message-ID: <20050630161726.GA11185@elte.hu> (raw)
In-Reply-To: <20050630154304.GA1298@us.ibm.com>
* Paul E. McKenney <paulmck@us.ibm.com> wrote:
> > another point is that this test is measuring the overhead of PREEMPT_RT,
> > without measuring the benefit of the cost: RT-task scheduling latencies.
> > We know since the rtirq patch (to which i-pipe is quite similar) that we
> > can achieve good irq-service latencies via relatively simple means, but
> > that's not what PREEMPT_RT attempts to do. (PREEMPT_RT necessarily has
> > to have good irq-response times too, but much of the focus went to the
> > other aspects of RT task scheduling.)
>
> Agreed, a PREEMPT_RT-to-IPIPE comparison will never be an
> apples-to-apples comparison. Raw data will never be a substitute for
> careful thought, right? ;-)
well, it could still be tested, since it's so easy: the dohell script is
already doing all of that as it runs rtc_wakeup - which runs a
SCHED_FIFO task and carefully measures wakeup latencies. If it is used
with 1024 Hz (the default) and it can be used in every test without
impacting the system load in any noticeable way.
Ingo
next prev parent reply other threads:[~2005-06-30 16:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 22:29 PREEMPT_RT and I-PIPE: the numbers, take 3 Kristian Benoit
2005-06-29 22:57 ` Bill Huey
2005-06-29 23:03 ` Andrea Arcangeli
2005-06-29 23:33 ` Bill Huey
2005-06-29 23:54 ` Paul E. McKenney
2005-06-30 1:50 ` Bill Huey
2005-06-30 1:56 ` Nick Piggin
2005-06-30 2:14 ` Bill Huey
2005-06-30 2:09 ` Nick Piggin
2005-06-30 2:18 ` Bill Huey
2005-06-30 6:50 ` Steven Rostedt
2005-06-30 14:15 ` Zwane Mwaikambo
2005-06-30 19:08 ` Bill Huey
2005-06-30 2:01 ` Nicolas Pitre
2005-06-30 2:16 ` Bill Huey
2005-06-30 2:19 ` Paul E. McKenney
2005-06-30 14:59 ` Bill Davidsen
2005-06-30 18:59 ` Bill Huey
2005-06-30 7:07 ` Ingo Molnar
2005-06-30 15:43 ` Paul E. McKenney
2005-06-30 16:17 ` Ingo Molnar [this message]
2005-06-30 16:48 ` Sven-Thorsten Dietrich
2005-06-30 23:08 ` Paul E. McKenney
2005-06-29 23:49 ` Paul E. McKenney
2005-06-30 5:55 ` Ingo Molnar
2005-06-30 10:32 ` Ingo Molnar
2005-06-30 16:55 ` 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=20050630161726.GA11185@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox