From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "gprizzi@domain.hid" <gprizzi@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] error in executing xenomai tests
Date: Thu, 06 Jan 2011 22:25:21 +0100 [thread overview]
Message-ID: <4D263341.1080601@domain.hid> (raw)
In-Reply-To: <12d5cebd852.gprizzi@domain.hid>
gprizzi@domain.hid wrote:
> Dear Sir,
>
> I find your considerations very useful, unfortunately I am not expert in tuning conventional
> operating system with real time patch.
>
> If you can help me I will greatly appreciate your advices.
>
> I run latency test and got the following results:
>
> root@domain.hid# ./latency
> == Sampling period: 100 us
> == Test mode: periodic user-mode task
> == All results in microseconds
> warming up...
> RTT| 00:00:01 (periodic user-mode task, 100 us period, priority 99)
> RTH|----lat min|----lat avg|----lat max|-overrun|---msw|---lat best|--lat worst
> RTD| -1.786| 2.224| 19.821| 0| 0| -1.786| 19.821
> RTD| -1.796| 2.330| 19.490| 0| 0| -1.796| 19.821
> RTD| -1.831| 2.231| 19.495| 0| 0| -1.831| 19.821
> RTD| -1.772| 2.291| 19.743| 0| 0| -1.831| 19.821
> RTD| -1.473| 2.460| 19.708| 0| 0| -1.831| 19.821
> RTD| -1.524| 2.381| 19.717| 0| 0| -1.831| 19.821
> RTD| -1.752| 2.338| 19.807| 0| 0| -1.831| 19.821
> RTD| -1.893| 2.297| 19.520| 0| 0| -1.893| 19.821
> RTD| -2.192| 2.284| 19.549| 0| 0| -2.192| 19.821
> RTD| -1.635| 2.327| 19.530| 0| 0| -2.192| 19.821
> RTD| -1.416| 2.406| 19.580| 0| 0| -2.192| 19.821
> RTD| -1.305| 2.471| 14.930| 0| 0| -2.192| 19.821
> RTD| -1.782| 2.409| 14.999| 0| 0| -2.192| 19.821
> RTD| -1.774| 2.364| 18.456| 0| 0| -2.192| 19.821
> RTD| -1.784| 2.328| 19.914| 0| 0| -2.192| 19.914
> RTD| -1.768| 2.293| 19.639| 0| 0| -2.192| 19.914
> RTD| -1.777| 2.263| 19.463| 0| 0| -2.192| 19.914
> RTD| -1.228| 2.389| 19.923| 0| 0| -2.192| 19.923
> RTD| -1.223| 2.405| 19.579| 0| 0| -2.192| 19.923
> RTD| -1.778| 2.431| 14.499| 0| 0| -2.192| 19.923
> RTD| -1.983| 2.493| 15.335| 0| 0| -2.192| 19.923
The info you are missing here, and which is not obvious, I admit, is
that by running latency 30 seconds on an idle system, you are not even
close of knowing the worst case latency of Xenomai on your system.
In order to evaluate the worst case latency of Xenomai on your system,
you have to run the latency test, for a long time, on a loaded system,
and with the frequency of the task whose latency you are interested in.
That said, I insist, unless you know or even have rough estimates of the
way your final application is behaving, this does not give you much of a
clue. Otherwise, you can not answer the question "is this latency
sufficient ?" right away, you have to wait for the application to be
developed and running.
--
Gilles.
next prev parent reply other threads:[~2011-01-06 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 20:01 [Xenomai-help] R: Re: R: Re: error in executing xenomai tests gprizzi
2011-01-06 20:39 ` [Xenomai-help] " Gilles Chanteperdrix
2011-01-06 21:25 ` Gilles Chanteperdrix [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-05 17:12 gprizzi
2011-01-05 17:32 ` Gilles Chanteperdrix
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=4D263341.1080601@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=gprizzi@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.