From: Jan Kiszka <jan.kiszka@domain.hid>
To: "M. Koehrer" <mathias_koehrer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Results of xenomai's latency test vs. RTAI's
Date: Mon, 30 Oct 2006 17:23:44 +0100 [thread overview]
Message-ID: <45462710.8040205@domain.hid> (raw)
In-Reply-To: <15328399.1162222490427.JavaMail.ngmail@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]
M. Koehrer wrote:
> Hi everybody,
>
> I have repeated the test using a parallel stress test (dd if=/dev/sda of=/dev/null, I have
> a SATA harddisk).
> The results are that my RTAI latency of 4µs is not valid, here the latency is about 26µs.
> However, xenomai shows a higher latency of about 40µs.
How long did the tests run this time? To my experience anything below 30
min. is not meaningful. And the faster the machines get, the lower the
probability for certain constellations becomes. So each additional hour
runtime gives a little bit more confidence.
> The interesting thing is, that without load RTAI seems to run very long in a very
> low latency region, at the same setup xenomai shows large latencies earlier.
>
>
> Well, I have repeated these tests on a different PC that has a server mainboard and
> a Pentium D 4 (real dual core) CPU.
> The results (measured under load) are much better here:
> RTAI shows a latency of about 6µs
> Xenomai shows a latency of about 10µs.
> Both values are acceptable, however I wonder where the difference comes from?
RTAI contains a few shortcuts that may explain parts of this gap, but
not all.
One of these shortcuts is the immediate IRQ dispatching mode (the reason
why they have their own patch...). In that mode the registered timer IRQ
handler gets called without caring about any I-pipe abstraction.
Some others I recall are a missing clean timer subsystem abstraction
(tasked are timed, and then there are also some kind of timer tasklets)
and the immediate reschedule from IRQ context instead of doing this on
IRQ return. Some of those features should be controllable via magic
knobs, maybe it's worth a try what they actually buy you here.
In any case, to really understand the differences, it takes the tracer.
I will check if I can find my old RTAI hack to instrument their latency
tool - if you are still interested in digging deeper on your hardware.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-10-30 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 10:05 [Xenomai-help] Results of xenomai's latency test vs. RTAI's latency test M. Koehrer
2006-10-30 10:22 ` Jan Kiszka
2006-10-30 11:05 ` Re: [Xenomai-help] Results of xenomai's latency test vs. RTAI's latency M. Koehrer
2006-10-30 11:39 ` Jan Kiszka
2006-10-30 11:37 ` [Xenomai-help] Results of xenomai's latency test vs. RTAI's latency test Philippe Gerum
2006-10-30 14:15 ` Re: [Xenomai-help] Results of xenomai's latency test vs. RTAI's M. Koehrer
2006-10-30 14:40 ` Philippe Gerum
2006-10-30 15:34 ` M. Koehrer
2006-10-30 16:23 ` Jan Kiszka [this message]
2006-10-30 16:24 ` Gilles Chanteperdrix
2006-10-30 17:44 ` Philippe Gerum
2006-10-30 16:39 ` Jan Kiszka
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=45462710.8040205@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=mathias_koehrer@domain.hid \
--cc=xenomai@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.