From: Philippe Gerum <rpm@xenomai.org>
To: Steven Seeger <steve@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>,
Jan Kiszka <jan.kiszka@domain.hid>
Subject: Re: [Xenomai-help] resume/suspend periodic timing issue
Date: Tue, 28 Feb 2006 16:10:43 +0100 [thread overview]
Message-ID: <440467F3.7020903@domain.hid> (raw)
In-Reply-To: <C0299D36.256C%steve@domain.hid>
Steven Seeger wrote:
> Every other RTOS I've ever used would disagree with you. However, I can wrap
set_periodic/wait_period are used to define a timeline, with a base period
dedicated to process a bounded work cycle. If your application decides to kill the
timeline by skipping work cycles voluntarily in order to process e.g. error states
or interactive break, it needs to reset the timeline by calling set_periodic anew,
which seems quite reasonable to do, since the old timeline is now dead in the
water. If this is not some error recovery work or break state, but regular
processing, then it should fit in the normal work cycle, otherwise there is no
point in using set_periodic/wait_period to time it in the first place.
Beyond that, comparing with other RTOS behaviours does not fly that well, because
some which actually implement this kind of construct might well raise an exception
to some health manager entity for signaling the overrun (e.g. arinc653), in which
case, one would end up having to hack the error handler so that it swallows those
exceptions silently, for the interesting purpose of making a valid case out of an
error case...
We could pass rt_task_wait_period() a pointer to an integer that would collect the
count of overruns, and reset this count after the first overrun has been signaled.
But this would not fix the initial problem in the application, though.
> the suspend/resume functions with a call to set period. Thanks for the tip.
>
> Steven
>
> On 2/28/06 6:21 AM, "Jan Kiszka" <jan.kiszka@domain.hid> wrote:
>
>
>>Steven Seeger wrote:
>>Just imagine that your task is attached to a continuously running timer
>>as soon as you request this via rt_task_set_periodic. So, if you feel
>>like suspending the task for a while, detach it from that timer again
>>(infinite period). Putting this functionality into the RTOS is a bit
>>overkill in my eyes.
>>
>>This is a corner use-case, so not everyone should pay for implementing
>>it in a generic way, only the user who really wants it (by having to
>>write a few extra lines).
>>
>>Jan
>>
>
>
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
--
Philippe.
next prev parent reply other threads:[~2006-02-28 15:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 14:20 [Xenomai-help] resume/suspend periodic timing issue Steven Seeger
2006-02-27 18:39 ` Gilles Chanteperdrix
2006-02-28 13:45 ` Steven Seeger
2006-02-28 13:55 ` Gilles Chanteperdrix
2006-02-28 14:07 ` Steven Seeger
2006-02-28 14:21 ` Jan Kiszka
2006-02-28 14:24 ` Steven Seeger
2006-02-28 15:10 ` Philippe Gerum [this message]
2006-02-28 15:13 ` Steven Seeger
2006-02-28 15:27 ` Jan Kiszka
2006-02-28 15:29 ` Steven Seeger
2006-02-28 15:43 ` Jan Kiszka
2006-02-28 15:46 ` Steven Seeger
2006-02-28 16:01 ` Jan Kiszka
2006-02-28 16:27 ` Steven Seeger
2006-02-28 15:29 ` Philippe Gerum
2006-02-28 15:31 ` Steven Seeger
2006-02-28 16:20 ` Philippe Gerum
2006-02-28 16:28 ` Steven Seeger
2006-02-28 16:37 ` Philippe Gerum
2006-02-28 17:24 ` Steven Seeger
2006-02-28 17:53 ` [Xenomai-core] rt_task_wait_period() and overruns Philippe Gerum
2006-02-28 18:02 ` [Xenomai-core] Re: [Xenomai-help] " Philippe Gerum
2006-02-28 18:15 ` Steven Seeger
2006-03-01 10:22 ` Philippe Gerum
2006-03-01 15:25 ` Dmitry Adamushko
2006-03-01 16:00 ` Philippe Gerum
2006-03-01 19:01 ` Dmitry Adamushko
2006-03-03 11:29 ` Philippe Gerum
2006-02-28 13:57 ` [Xenomai-help] resume/suspend periodic timing issue Philippe Gerum
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=440467F3.7020903@domain.hid \
--to=rpm@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=steve@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.