On Fri, 2006-06-23 at 11:48 +0200, ROSSIER Daniel wrote: > > > Hi all, > > > > Is there a particular reason to enforce the queuing policy to the > "highest priority" thread for a variable condition? >
The reason was that condvar support for the native skin should closely follow the POSIX behaviour, which uses the scheduling policy to define the pending order of threads blocked on mutexes/condvars. > I would expect that we can also specify a FIFO queue at the creation > mode of such an object, as it is the case > of other synchronization objects. The problem I see is that a condvar must be associated with a mutex, and since a mutex must be pended on by priority and exhibits priority inheritance by construction, I would find rather strange to have part of the synchronization combo behave in fifo mode, whilst the other part enforces prio mode. > > > > Thanks for your help. > > > > Daniel > > > > > _______________________________________________ > Xenomai-core mailing list > Xenomai-core@gna.org > https://mail.gna.org/listinfo/xenomai-core -- Philippe. _______________________________________________ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
