From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Yogi A. Patel" <yapatel@gatech.edu>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Build Xenomai Lib native on the Beaglebone Black
Date: Wed, 12 Mar 2014 13:29:58 +0100 [thread overview]
Message-ID: <53205346.6020605@xenomai.org> (raw)
In-Reply-To: <3F7844F7-FC18-44C3-A946-528C28CB81AC@gatech.edu>
On 03/12/2014 12:59 AM, Yogi A. Patel wrote:
> Flavio -
>
> Would you mind sharing what latencies you are seeing on your Beaglebone black with xenomai?
Some results which might be interesting, the results for the IGEPv2
board, using an omap3630 processor, close to the beaglebone black
processor, are in the 40-45us range, if the kernel is compiled with the
right options, that is:
- kernel built using thumb2 and optimized for size
- preemption set to CONFIG_PREEMPT_NONE
- CONFIG_SMP disabled
- stack unwinding enabled
- xenomai unlocked switch disabled
- all xenomai/ipipe debugs off, except maybe "watchdog support" and
"detect mutexes held in relaxed sections", as they should not incur an
increase in latency.
Since the I-pipe core series (so since linux 3.2), I have started
recording the results I get on the test platforms I have, see, to show
the improvements over time (most improvements are due to configurations
changes):
http://xenomai.org/~gch/core-3.2-latencies/
http://xenomai.org/~gch/core-3.4-latencies/
http://xenomai.org/~gch/core-3.5-latencies/
http://xenomai.org/~gch/core-3.8-latencies/
http://xenomai.org/~gch/core-3.10-latencies/
Note that we recently discovered that disabling the L2 cache
"write-allocate" bit on imx6 and omap4, so probably on any multi-core
cortex a9, improved latencies considerably, and that moving the
spinlocks code out-of-line did too, see:
http://sisyphus.hd.free.fr/~gilles/panda-test/inline-spinlocks.png
The change of the L2 write-allocate bit will be in the next Xenomai 2.x
release, whereas the change of spinlock code will only appear in xenomai
3.0.
Anyway, I would like to also try disabling the L2 cache write-allocate
on omap3, but IGEPv2 is running in secure mode, so I can not change this
configuration, I would probably need an "smc" call, but I have not found
a documentation for these calls, so if anyone knows where to find this
info, I am interested.
Regards.
--
Gilles.
next prev parent reply other threads:[~2014-03-12 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 23:59 [Xenomai] Build Xenomai Lib native on the Beaglebone Black Yogi A. Patel
2014-03-12 12:29 ` Gilles Chanteperdrix [this message]
2014-03-16 21:37 ` Yogi A. Patel
2014-03-16 23:47 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2014-03-10 3:00 Flavio Castro Alves Filho
2014-03-10 6:49 ` Gilles Chanteperdrix
2014-03-10 14:57 ` Flavio Castro Alves Filho
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=53205346.6020605@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.org \
--cc=yapatel@gatech.edu \
/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.