From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Tschaeche IT-Services <services@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Scheduling clarification/solution...
Date: Tue, 11 May 2010 21:09:58 +0200 [thread overview]
Message-ID: <4BE9AB86.5040805@domain.hid> (raw)
In-Reply-To: <20100511142653.GA22374@domain.hid>
Tschaeche IT-Services wrote:
> Hi,
>
> having done some tests and having read the thread
> https://mail.gna.org/public/xenomai-help/2010-04/msg00051.html
> i got the following understanding:
You are summarizing stuff explained in Xenomai documentation:
http://www.xenomai.org/documentation/branches/v2.3.x/pdf/Life-with-Adeos-rev-B.pdf
http://www.xenomai.org/documentation/branches/v2.3.x/pdf/Native-API-Tour-rev-C.pdf
http://www.xenomai.org/index.php/Porting_POSIX_applications_to_Xenomai
To be consistent, when a task is scheduled by Xenomai scheduler, we say
it is in "primary mode", whereas when scheduled by Linux scheduler, we
say it is in "secondary mode". Since this is the terminology we chose,
you would probably better stick to it than using other terms.
> (...)
> Linux/Posix calls. (on the other side Linux/Posix calls
> does not control priority when in RT xenomai state).
I do not really understand what you mean. The priorities are fully
propagated between the two schedulers. If you call phtread_setschedparam
or sched_setscheduler, the priority should be propagated to a Xenomai
thread.
--
Gilles.
prev parent reply other threads:[~2010-05-11 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 14:26 [Xenomai-help] Scheduling clarification/solution Tschaeche IT-Services
2010-05-11 16:20 ` Jan Kiszka
2010-08-05 14:51 ` [Xenomai-help] Forcing a task to run in secondary mode if no RT resources are acquired Tschaeche IT-Services
2010-05-11 19:09 ` Gilles Chanteperdrix [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=4BE9AB86.5040805@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=services@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.