From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Dominique.RAGOT@fr.thalesgroup.com
Cc: xenomai@xenomai.org
Subject: RE: [Xenomai-help] number-crunching execution jitter
Date: Mon, 7 Nov 2005 23:06:04 +0100 [thread overview]
Message-ID: <17263.53196.315176.630084@domain.hid> (raw)
In-Reply-To: <2F8EE677D406514ABE53EF9C0934A666017CAF3E@anubis2.clb.tcfr.thales>
Dominique.RAGOT@fr.thalesgroup.com wrote:
> In the meantime I modified the benchmark with a call to the routine
> pthread_set_mode_np(0, PTHREAD_SHIELD) immediately after thread is
> created, and observes a huge reduction in execution jitter, but at
> the expense of wakeup jitter. So I concluded the interrupt shield was
> definitely not doing much without this call. Am I wrong ?
I guess Philippe and Stephane gave you answers regarding the way to
activate the shield (I did not check if pthread_set_mode fails when the
shield was disabled at compilation time and is used at run time, if not,
maybe it would be a good idea ?).
Now about the wakeup jitter, if you are still using the "cruncher" as in
RTAI/Fusion, what is called "nanosleep jitter" may not be a precise
measurement of the wakeup latency. A better measurement of the
scheduling latency using the POSIX skin is obtained using the
clock_nanosleep call with the TIMER_ABSTIME flag, pass an absolute time,
and measure the difference between this time and the wakeup time.
Also note that CLOCK_MONOTONIC will give better accuracy than
CLOCK_REALTIME, since it is using the tsc even when system timer is in
periodic mode.
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2005-11-07 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 17:11 [Xenomai-help] number-crunching execution jitter Dominique.RAGOT
2005-11-06 19:44 ` Philippe Gerum
2005-11-07 22:06 ` Gilles Chanteperdrix [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-04 12:30 Fillod Stephane
2005-11-03 13:59 Dominique.RAGOT
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=17263.53196.315176.630084@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Dominique.RAGOT@fr.thalesgroup.com \
--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.