From: john cooper <john.cooper@timesys.com>
To: karim@opersys.com
Cc: Andrew Morton <akpm@osdl.org>,
paulmck@us.ibm.com, linux-kernel@vger.kernel.org, mingo@elte.hu,
rpm@xenomai.org, john cooper <john.cooper@timesys.com>
Subject: Re: [RFC][PATCH] Restricted hard realtime
Date: Thu, 28 Oct 2004 09:04:22 -0400 [thread overview]
Message-ID: <4180EE56.4030100@timesys.com> (raw)
In-Reply-To: <4180DDFA.1050409@opersys.com>
Karim Yaghmour wrote:
> Usually one of the litmus tests for this is to hook a function
> generator to the system and inject a square wave through an
> interrupt-generating I/O (ex.: parallel port), while measuring the
> response time of an interrupt service routine and comparing it to
> the input wave using an oscilloscope. One sign that the system is
> indeed deterministic is that both square waves should appear
> steady regardless of the load.
Ideally yes, but there will still be some phase modulation
due to the natural randomness of interrupt masking for hard
irqs and from scheduling preemption latency for irqs run in
task context. Also contributing to this will be latency
due to interrupt hardware which may not be constant.
One likely observation will be increased contention
from periodic interrupt sources (clock) with the injected
square wave interrupt when these frequencies (or their
harmonics) approach each other. The contention would
appear periodic at the difference of these interrupt
frequencies.
Other sources of phase bobble will include variable
CPU cache content, loading of the bus from other DMA
masters, SMP bus contention, etc.. which are much more
difficult to address.
-john
--
john.cooper@timesys.com
next prev parent reply other threads:[~2004-10-28 13:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 19:47 [RFC][PATCH] Restricted hard realtime Paul E. McKenney
2004-10-23 20:17 ` Ingo Molnar
2004-10-23 20:29 ` Paul E. McKenney
2004-10-24 18:18 ` Paul E. McKenney
2004-10-25 12:26 ` Dimitri Sivanich
2004-10-23 20:22 ` Thomas Gleixner
2004-10-23 21:24 ` Paul E. McKenney
2004-10-23 22:06 ` Jon Masters
2004-10-24 15:32 ` Paul E. McKenney
2004-10-24 21:08 ` Jon Masters
2004-10-24 21:23 ` Ingo Molnar
2004-10-24 21:49 ` Jon Masters
2004-10-24 21:52 ` Paul E. McKenney
2004-10-27 3:16 ` Karim Yaghmour
2004-10-27 4:29 ` Andrew Morton
2004-10-27 8:10 ` Ingo Molnar
2004-10-28 11:59 ` Karim Yaghmour
2004-10-28 13:16 ` Ingo Molnar
2004-10-28 11:54 ` Karim Yaghmour
2004-10-28 13:04 ` john cooper [this message]
2004-10-27 22:35 ` Bill Huey
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=4180EE56.4030100@timesys.com \
--to=john.cooper@timesys.com \
--cc=akpm@osdl.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@us.ibm.com \
--cc=rpm@xenomai.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 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.