From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Haberler <mail17@mah.priv.at>
Cc: Schooner <schooner30@tiscali.co.uk>,
sam sokolik <samco@empirescreen.com>,
John Morris <john@zultron.com>,
xenomai@xenomai.org
Subject: Re: [Xenomai] puzzled: running switchtest improves latency figures permanently
Date: Wed, 13 Feb 2013 12:53:55 +0100 [thread overview]
Message-ID: <511B7ED3.8060106@xenomai.org> (raw)
In-Reply-To: <F43474DF-1ADA-4463-AF44-2B498EF3024E@mah.priv.at>
On 02/13/2013 10:26 AM, Michael Haberler wrote:
>
> We have a report from 'the field' which we cannot make sense of.
>
> The situation:
> - an AMD board: http://www.asus.com/Motherboard/F1A75M_PRO
> - dmesg post boot: http://pastebin.com/38XrxNBy
> - xeno-regression-test runs well, max 32us jitter
Please do not rely on latency results with xeno-regression-test,
switchtest artificially increases latencies by locking the scheduler.
The tool to make latency benchmarks is xeno-test.
> what we observed:
>
> 1. Problem behaviour
> ---------------------
> - boot
> - run LinuxCNC latency-test
> - observe massive spikes in latency
> - >100uS on a 25uS thread!
> - http://static.mah.priv.at/public/latency/skunkworks-unprimed.png
Do you get the same results with Xenomai latency test?
> now any of 2), 3) or 4) improve latency:
> - running "/usr/lib/xenomai/testsuite/switchtest -s 1000" in a separate
> - while true; do echo "nothing" > /dev/null; done
> - the key observation: if you break by ^C out of xeno-regression-test, *latency
> figures remain low*
> - note that breaking out of xeno-regression-test left some processes running, obviously dd and ls: http://pastebin.ca/2313116
Yes, that is a known behaviour of dohell. Fixing this in a manner
portable accross various shell implementations proved to be a task not
as easy as it seems. So, for the sake of simplicity, we simply ignore
the problem, xeno-regression-test or xeno-test are meant to be run not
very often, so a reboot after running them, or manually kill the task is
not much of an issue.
> Any suggestions?
You have an issue with the idle loop. The three cases you mention cause
the Linux kernel never to use the idle loop:
- switchtest run with the -s argument as a (non real-time) loop
occupying 100% of the CPU.
- the shell loop does the same
- running dohell does the same.
--
Gilles.
next prev parent reply other threads:[~2013-02-13 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DC570CF5-F540-40FB-B313-596AF53EDDA2@mah.priv.at>
2013-02-13 9:26 ` [Xenomai] puzzled: running switchtest improves latency figures permanently Michael Haberler
2013-02-13 9:49 ` Henri Roosen
2013-02-13 10:01 ` Jan Kiszka
2013-02-13 10:06 ` Jan Kiszka
2013-02-13 11:55 ` Gilles Chanteperdrix
2013-02-13 11:53 ` Gilles Chanteperdrix [this message]
2013-02-13 14:35 ` Michael Haberler
2013-02-13 19:39 ` 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=511B7ED3.8060106@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=john@zultron.com \
--cc=mail17@mah.priv.at \
--cc=samco@empirescreen.com \
--cc=schooner30@tiscali.co.uk \
--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.