From: Philippe Gerum <rpm@xenomai.org>
To: Registrierungen <regist@bmwedler.de>
Cc: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
xenomai@xenomai.org
Subject: Re: [Xenomai] Alchemy periodic task and timer overruns
Date: Mon, 30 Nov 2015 16:46:34 +0100 [thread overview]
Message-ID: <565C6F5A.2090209@xenomai.org> (raw)
In-Reply-To: <20151130120930.GA19802@hermes.click-hack.org>
On 11/30/2015 01:09 PM, Gilles Chanteperdrix wrote:
> On Mon, Nov 30, 2015 at 11:57:49AM +0100, Registrierungen wrote:
>> Hello,
>>
>> i've got a problem using the periodic tasks.
>> I am using the alchemy tasks running 10kHz and i get a lot of (up ~
>> 10) timer overruns / sek calling rt_task_wait_period. (each overrung
>> has an amount of 1 ).
>>
>> I extracted the task to a test program. In this example he is doing
>> nothing between the rt_task_wait_period calls.
>> Ironically i get more (up ~ 100) timer overruns / sek calling
>> rt_task_wait_period.
>>
>> I am running a AMD-G Series, x86_64 with SMP.
>> I tested on xenomai 3rc2 and xenomai 3.0.1 (with optimized kernel,
>> following the documentation) with same results.
>>
>> Any idea, what is going wrong?
>> How can i find out where is the problem?
>
> Do you observe the same problem with xenomai "latency" test? If yes,
> then using the I-pipe tracer should help you. Note that all that is
> documented in the "troubleshooting" guide:
>
> http://xenomai.org/troubleshooting-a-dual-kernel-configuration/#the_latency_test_shows_high_latencies
>
Also, demo/altency implements the very same latency test using the
alchemy API, with rt_task_wait_period() and friends. You may want to
check whether such test works fine on your platform.
--
Philippe.
prev parent reply other threads:[~2015-11-30 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 10:57 [Xenomai] Alchemy periodic task and timer overruns Registrierungen
2015-11-30 12:09 ` Gilles Chanteperdrix
2015-11-30 15:46 ` Philippe Gerum [this message]
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=565C6F5A.2090209@xenomai.org \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=regist@bmwedler.de \
--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.