From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Christophe Blaess <mailist@logilin.fr>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] question: XENO_OPT_TIMING_SCHEDLAT
Date: Sat, 30 Jun 2012 19:04:44 +0200 [thread overview]
Message-ID: <4FEF31AC.2000403@xenomai.org> (raw)
In-Reply-To: <4FEF2EB1.3050600@logilin.fr>
On 06/30/2012 06:52 PM, Christophe Blaess wrote:
> On 30/06/2012 12:44, Gilles Chanteperdrix wrote:
>>
>>> /proc/xenomai/latency is an estimation of the minimum scheduling latency
>>> on your system. In order to know what to put there you should do:
>>>
>>> echo 0 > /proc/xenomai/latency
>>>
>>> Run latency under load for several hour
>
> Is it necessary to run the test under heavy load?
> We're looking for the minimal latency, not the worst.
>
> I thought that in this case a normal, even light load would be sufficient.
It is not obvious which path is the shortest. For instance, having to
wake up from a "wait for interrupt" state to handle the timer interrupt
may induce a certain latency, and so may not be the shortest path. So,
running the test for a long time, and with a lot of different activities
is an empiric way to try many paths so that extreme paths have more
chances to be closest to the extrema paths.
And anyway, you usually want to know the worst case latency for your
system as well.
--
Gilles.
next prev parent reply other threads:[~2012-06-30 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 10:39 [Xenomai] question: XENO_OPT_TIMING_SCHEDLAT ali hagigat
2012-06-30 10:44 ` Gilles Chanteperdrix
2012-06-30 16:52 ` Christophe Blaess
2012-06-30 17:04 ` Gilles Chanteperdrix [this message]
2012-07-01 19:00 ` Christophe Blaess
2012-07-01 19:09 ` Gilles Chanteperdrix
2012-07-01 19:33 ` Gilles Chanteperdrix
2012-07-02 6:12 ` Christophe Blaess
2012-07-02 7:11 ` Christophe Blaess
2012-07-02 8:47 ` 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=4FEF31AC.2000403@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=mailist@logilin.fr \
--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.