From: Jan Kiszka <jan.kiszka@domain.hid>
To: Henri Roosen <henriroosen@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] New scheduler class
Date: Fri, 02 Apr 2010 12:07:17 +0200 [thread overview]
Message-ID: <4BB5C1D5.8030804@domain.hid> (raw)
In-Reply-To: <k2rb88603c31004020243k8d9681f8y453b25393bb5d3a0@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Henri Roosen wrote:
> Actually that is what I thought in the first place, however Jan's
> comment "That's not true, Xenomai threads can run in non-RT scheduling
> classes as well. They may just gain RT priority while holding some
> lock that is requested by a RT thread as well." made me think I was
> wrong...
>
> So we would really need a SCHED_IDLE for Xenomai then to solve this problem?
I don't think so. But we do need to solve the issue that a non-RT thread
stays too long in primary mode and is thus scheduled by Xenomai with the
wrong priority /wrt other Linux task at its level.
For the time being, you can work around this by issuing a Linux syscall
before entering long processing loops - unless your task doesn't do this
anyway, e.g. to perform some Linux I/O.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-04-02 10:07 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 23:08 [Xenomai-help] New scheduler class Andreas Glatz
2010-04-02 0:08 ` Jan Kiszka
2010-04-02 0:11 ` Gilles Chanteperdrix
2010-04-02 7:58 ` Henri Roosen
2010-04-02 8:06 ` Gilles Chanteperdrix
2010-04-02 8:27 ` Gilles Chanteperdrix
2010-04-02 9:18 ` Jan Kiszka
2010-04-02 9:24 ` Jan Kiszka
2010-04-02 9:27 ` Gilles Chanteperdrix
2010-04-02 9:32 ` Henri Roosen
2010-04-02 9:34 ` Gilles Chanteperdrix
2010-04-02 9:43 ` Henri Roosen
2010-04-02 10:07 ` Jan Kiszka [this message]
2010-04-04 23:04 ` Andreas Glatz
2010-04-06 6:45 ` Jan Kiszka
2010-04-15 0:19 ` Andreas Glatz
2010-04-15 9:02 ` Philippe Gerum
2010-04-20 14:12 ` Andreas Glatz
2010-04-23 10:54 ` Philippe Gerum
2010-09-30 12:52 ` Henri Roosen
2010-09-30 13:29 ` Gilles Chanteperdrix
2010-10-04 11:02 ` Philippe Gerum
2010-10-04 13:14 ` Henri Roosen
2010-10-10 21:17 ` Philippe Gerum
2010-04-15 10:46 ` Philippe Gerum
2010-04-15 12:36 ` Andreas Glatz
2010-04-15 12:40 ` Gilles Chanteperdrix
2010-04-15 12:59 ` Andreas Glatz
2010-04-15 13:15 ` Gilles Chanteperdrix
2010-04-16 15:29 ` Andreas Glatz
2010-04-16 15:57 ` Gilles Chanteperdrix
2010-04-02 10:00 ` Jan Kiszka
2010-04-02 10:02 ` Gilles Chanteperdrix
2010-04-02 8:26 ` Jan Kiszka
2010-04-02 8:29 ` Gilles Chanteperdrix
2010-04-02 8:58 ` Jan Kiszka
2010-04-02 9:03 ` Jan Kiszka
2010-04-02 9:24 ` Gilles Chanteperdrix
2010-04-02 10:02 ` Jan Kiszka
2010-04-02 10:05 ` Gilles Chanteperdrix
2010-04-02 10:12 ` Jan Kiszka
[not found] <mailman.6356.1286778008.12503.xenomai@xenomai.org>
2010-10-11 9:31 ` Andreas Glatz
2010-10-11 15:35 ` Henri Roosen
2010-10-12 7:16 ` Henri Roosen
2011-03-28 10:56 ` Henri Roosen
2011-03-28 11:44 ` Philippe Gerum
2011-05-01 15:01 ` Philippe Gerum
2011-05-02 8:58 ` Henri Roosen
2011-05-05 13:55 ` Philippe Gerum
2011-05-05 14:40 ` Henri Roosen
2011-06-28 9:26 ` Henri Roosen
2011-06-28 9:33 ` 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=4BB5C1D5.8030804@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=henriroosen@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.