From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] a question about ADEOS
Date: Wed, 30 May 2012 20:40:14 +0200 [thread overview]
Message-ID: <4FC6698E.2090800@xenomai.org> (raw)
In-Reply-To: <20120530175754.GL32727@csclub.uwaterloo.ca>
On 05/30/2012 07:57 PM, Lennart Sorensen wrote:
> On Wed, May 30, 2012 at 06:53:00PM +0200, Gilles Chanteperdrix wrote:
>> You can see for yourself with the xenomai-forge branch. It is already in
>> a usable state. I do not buy the scheduler argument: the linux scheduler
>> does pretty much the same separation between real-time and non real-time
>> tasks as the separation which happens with xenomai. And the scheduler
>> for real-time tasks is simple, it does not need to know much more than
>> the tasks priorities, I do not see what more you would like to control.
>
> I have been looking at it a bit. Maybe I should give it a try soon.
>
> Based on what I have seen for the real time linux patches, you can set
> priorities of kernel threads as well, which would be nice at times.
I am not sure to get what you mean, Xenomai kernel threads priority are
configurable as well.
>
> Perhaps our use is just not normal, in that we ahve an application that
> uses realtime, but has some work to do that is very low priority (and
> not in need of realtime) but needs to share memory space and resources
> with the stuff that does have to be real time, which makes it hard to
> make linux tasks run before the less important stuff in the xenomai
> application runs. It works using an idle priority thread, but it would
> be nice to have better control of it, which I hope the rt patches for
> linux would allow. Maybe I am hoping for too much.
Starting with Xenomai 2.6, if you create a xenomai thread with
scheduling policy SCHED_OTHER (and priority 0), it returns to secondary
mode as soon as possible, so, is handled by Linux scheduler as a low
priority thread most of the time. If this task is cpu bound, you
probably can even decrease its time slices by using the renice() service.
--
Gilles.
next prev parent reply other threads:[~2012-05-30 18:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 14:35 [Xenomai] a question about ADEOS ali hagigat
2012-05-30 14:57 ` Chris Stone
2012-05-30 15:08 ` Philippe Gerum
2012-05-30 15:27 ` Gilles Chanteperdrix
2012-05-30 15:57 ` Lennart Sorensen
2012-05-30 16:53 ` Gilles Chanteperdrix
2012-05-30 17:57 ` Lennart Sorensen
2012-05-30 18:40 ` Gilles Chanteperdrix [this message]
2012-05-30 17:32 ` Chris Stone
2012-05-30 17:59 ` Lennart Sorensen
2012-05-30 21:40 ` Gilles Chanteperdrix
2012-05-31 15:10 ` Chris Stone
2012-06-05 6:26 ` ali hagigat
2012-06-05 7:10 ` Philippe Gerum
2012-06-05 8:06 ` [Xenomai] ftrace dietmar.schindler
2012-06-05 8:17 ` Philippe Gerum
2012-06-13 9:32 ` dietmar.schindler
2012-06-13 9:49 ` Wolfgang Grandegger
2012-06-13 10:00 ` Wolfgang Grandegger
2012-06-05 7:20 ` [Xenomai] a question about ADEOS 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=4FC6698E.2090800@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=lsorense@csclub.uwaterloo.ca \
--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.