We have the same requirement for which we also have no solution. One
of our threads has a configurable priority of which at the lowest
priority the thread should behave like an idle task that is only
scheduled when all xenomai threads are idle and also the Linux domain
is idle. The thread might use rtdm-drivers and xenomai mutexes and
therefore has to be moved to the Xenomai domain. But then it always
has higher priority than any threads scheduled in linux.

Actually, when seen from the first domain, this requirement would be
solved when we could set a first domain priority for the second
domain... Gilles, is that what is meant by the SCHED_IDLE policy for
Linux?


On Fri, Apr 2, 2010 at 2:11 AM, Gilles Chanteperdrix
<[email protected]> wrote:
> Jan Kiszka wrote:
>> Andreas Glatz wrote:
>>> Hi Philippe,
>>>
>>> At the Xenomai Users Meeting last year I asked you if Xenomai would offer a 
>>> possibility to lower the priority of certain Xenomai tasks below that of 
>>> Linux. We need this feature since we have tasks in our RT application which 
>>> should only run when Linux is idle (A statistics collection task which part 
>>> of the RT application and hard to isolate from this application).
>>>
>>
>> What prevents using a borderline thread (if you need to interact with
>> blocking Xenomai services) with SCHED_OTHER and a Linux nice level of 19?
>
> Well, this does not really guarantee that the thread will run only when
> linux is idle. The thread will eat some cpu time, the nice level is not
> a strict priority, as you know. But in fact, I wonder why Andreas wants
> a new scheduling policy for xenomai, what is needed, is simply a
> SCHED_IDLE (maybe it exists ?!) policy for Linux.
>
> --
>                                            Gilles.
>
> _______________________________________________
> Xenomai-help mailing list
> [email protected]
> https://mail.gna.org/listinfo/xenomai-help
>

_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help

Reply via email to