From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Attempted summary of "RT patch acceptance" thread, take 2
Date: Mon, 11 Jul 2005 10:19:10 -0700 [thread overview]
Message-ID: <20050711171910.GE1304@us.ibm.com> (raw)
In-Reply-To: <1121100589.7050.24.camel@c-67-188-6-232.hsd1.ca.comcast.net>
On Mon, Jul 11, 2005 at 09:49:48AM -0700, Daniel Walker wrote:
> On Mon, 2005-07-11 at 09:43 -0700, Paul E. McKenney wrote:
> > Hello, Daniel,
> >
> > In principle, one could inspect the Linux kernel with the PREEMPT_RT patch
> > applied, and calculate the worst-case time during which interrupts are
> > disabled, though I have not heard of anyone actually doing this. Is this
> > what you are getting at, or are you thinking in terms of Kristian's and
> > Karim's testing?
>
> Well with the PREEMPT_RT patch applied the interrupt off sections are
> reduced to a small number, ~100 irrespective of config options or
> drivers (although I think APM might be the one exception) .
>
> So with the patch applied it becomes trivial to test/inspect each of the
> interrupt off sections , and thus give a hard guarantee for _all_
> PREEMPT_RT kernels.
OK, interesting point, though this would apply only to interrupt latency,
not to scheduling latency or to latency for any other system services,
right?
Do you believe that the 50-us delay measured by Kristian and Karim was
due to APM or due to hardware (as Karim suspected)? If the latter,
any guesses as to the cause of the holdup? 50 us is a -really- long
time for ~100 instructions on today's hardware, even if each instruction
misses the cache!
Thanx, Paul
next prev parent reply other threads:[~2005-07-11 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 14:55 Attempted summary of "RT patch acceptance" thread, take 2 Paul E. McKenney
2005-07-11 16:11 ` Daniel Walker
2005-07-11 16:43 ` Paul E. McKenney
2005-07-11 16:49 ` Daniel Walker
2005-07-11 17:19 ` Paul E. McKenney [this message]
2005-07-11 17:25 ` Daniel Walker
2005-07-13 14:29 ` Paul E. McKenney
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=20050711171910.GE1304@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=dwalker@mvista.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