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: Wed, 13 Jul 2005 07:29:18 -0700 [thread overview]
Message-ID: <20050713142918.GA1304@us.ibm.com> (raw)
In-Reply-To: <1121102728.7050.29.camel@c-67-188-6-232.hsd1.ca.comcast.net>
On Mon, Jul 11, 2005 at 10:25:28AM -0700, Daniel Walker wrote:
> On Mon, 2005-07-11 at 10:19 -0700, Paul E. McKenney wrote:
>
> > OK, interesting point, though this would apply only to interrupt latency,
> > not to scheduling latency or to latency for any other system services,
> > right?
>
> Only for interrupt latency, that I know of.
>
> > 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!
>
> There are ~100 interrupt off critical sections. Those sections can be
> variable numbers of instructions. I would imagine that whatever maximum
> latency that Kristian and Karim found is the maximum for their hardware.
Does your ~100-instruction estimate include scheduler_tick() interrupt?
>From another thread, I gather that it runs with hardware interrupts
disabled.
Thanx, Paul
prev parent reply other threads:[~2005-07-13 14:28 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
2005-07-11 17:25 ` Daniel Walker
2005-07-13 14:29 ` Paul E. McKenney [this message]
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=20050713142918.GA1304@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