From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: rpm@xenomai.org
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] rt_task_set_priority vs. Linux priority
Date: Thu, 02 Oct 2008 18:18:31 +0200 [thread overview]
Message-ID: <48E4F457.4000004@domain.hid> (raw)
In-Reply-To: <48E4F2E9.2020909@domain.hid>
Philippe Gerum wrote:
> AFAIC, I don't see how changing priorities on the fly within a time critical
> section could be considered as good programming practice; this would tend to
> indicate that somebody is playing with priorities to paper over an application
> design issue.
So, you mean PIP papers over application design issues ? Just kidding...
> For that reason, enduring a mode switch upon
> rt_task_set_priority() calls (and friends) would be ok for me. But that's
> certainly debatable.
Actually, we could trigger a signal for pthread_setschedparam to be
called for next switch to secondary mode. We could re-use the signal
already used to trigger a switch to primary mode for suspending a thread
running in secondary mode, finding a way to multiplex the information
passing, for instance, parameters to the siginfo structure.
--
Gilles.
next prev parent reply other threads:[~2008-10-02 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 15:51 [Xenomai-core] rt_task_set_priority vs. Linux priority Jan Kiszka
2008-10-02 15:52 ` Gilles Chanteperdrix
2008-10-02 16:06 ` Gilles Chanteperdrix
2008-10-02 16:06 ` Jan Kiszka
2008-10-02 16:10 ` Gilles Chanteperdrix
2008-10-02 16:18 ` Jan Kiszka
2008-10-02 16:30 ` Philippe Gerum
2008-10-02 16:37 ` Gilles Chanteperdrix
2008-10-02 16:48 ` Philippe Gerum
2008-10-02 16:12 ` Philippe Gerum
2008-10-02 16:18 ` Gilles Chanteperdrix [this message]
2008-10-02 16:23 ` Jan Kiszka
2008-10-02 16:26 ` Jan Kiszka
2008-10-02 16:45 ` 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=48E4F457.4000004@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=rpm@xenomai.org \
--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.