All of lore.kernel.org
 help / color / mirror / Atom feed
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 latency
Date: Mon, 30 Oct 2006 12:39:03 +0100	[thread overview]
Message-ID: <4545E457.2080103@domain.hid> (raw)
In-Reply-To: <33139598.1162206356611.JavaMail.ngmail@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]

M. Koehrer wrote:
> Hi Jan,
> 
> thanks for your reply.
> 
>>> I am currently checking XENOMAI (V2.2.3 on a 2.6.17.7 kernel P4) to see if
>> I can use it
>>> as replacement for a RTAI 3.3-cv application.
>>> The first thing I did was to run the latency test in the the xenomai's
>> testsuite directory.
>>> The results of the worst time latency are really ugly - about 40µs!
>>> On the very same PC I got a value of about 5µs using RTAI 3.3-cv running
>> the RTAI's
>>> user/latency test.
>> I'm _very_ sceptical about your 5 us. Could you elaborate on how you
>> load your box and how long those tests ran? See also TROUBLESHOOTING in
>> the Xenomai source tree on appropriate load for triggering the worst case.
> 
> My test setup was the same in both cases.
> I connect to the RTAI/Xenomai PC via telnet and let the latency test run for about 5 minutes.

5 min. are far too short.

It takes a while to "arrange" the worst case, i.e. a dirty cache, one
unrelated IRQ or atomic section running while the timer (or any other
event of interest) occurs, and then one or more further IRQs right after
the woken-up task re-enabled interrupts. If you hit such scenario can be
observed via the latency tracer (which has some impact on the numbers,
but not on the structuring).

> No other activity happens (well, there are a couple of services running like
> apache, ... - but they should not cause any load).
> The strange thing, is that in Xenomai even after a few seconds a latency in the range of the
> maximum latency is shown.

Such a test on an unloaded system says almost nothing about a hard
real-time system.

> 
> I can retry the tests using a background stress situation.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2006-10-30 11:39 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 [this message]
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
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=4545E457.2080103@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.