From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Eric Eric <ericrebates@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] in-kernel periodic task latencies caused by dohell
Date: Tue, 07 Feb 2012 16:22:58 +0100 [thread overview]
Message-ID: <4F3141D2.7000605@domain.hid> (raw)
In-Reply-To: <CAMak2D-YfDCvjbZiLFYGntYdDCJVPiYtwt5z8k=PPT-9yj3S5A@mail.gmail.com>
On 02/07/2012 01:01 AM, Eric Eric wrote:
> Hello, I've been doing some more Xenomai benchmarking lately and have come
> across what seems to be strange behavior. I'm running Xenomai 2.6.0 on a
> Beagleboard XM with kernel 2.6.37. Just running the in-kernel periodic
> task benchmark (./latency -t1) alone results in an average of 2.7uS
> latency. What is interesting is the effect of various parts of dohell:
>
> 1) If I just run unmodified dohell with only the seconds argument, the
> latency goes to about 17uS.
>
> 2) If I comment out all tests in dohell except for "dd if=/dev/zero
> of=/dev/null &", average latency goes to 3.3uS (with top indicating about
> 98% CPU usage by dd).
>
> 3) If I comment out all tests in dohell except for "while :; do cat
> /proc/interrupts; done > /dev/null 2>&1 &", average latency goes to about
> 24uS.
>
> So it seems that trapping into the Linux kernel can have a drastic effect
> on Xenomai real-time kernel latencies.
You are drawing conclusions a bit too fast. dd also causes a lot of
trapping into the kernel. If you are interested in knowing how the time
is spent, I suggest using the I-pipe tracer.
If you find an improvement of the I-pipe patch for your platform, we
will gladly welcome patches.
--
Gilles.
next prev parent reply other threads:[~2012-02-07 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 0:01 [Xenomai-help] in-kernel periodic task latencies caused by dohell Eric Eric
2012-02-07 15:22 ` Gilles Chanteperdrix [this message]
2012-02-08 0:25 ` Eric Eric
2012-02-08 12:16 ` 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=4F3141D2.7000605@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=ericrebates@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.