On Thu, 21 Oct 2004, john cooper wrote:That more/less falls out of the PI mechanism. Though it
Mutexes layered on existing semaphores seems convenient
at the moment. However a more native mutex mechanism
which tracks ownership would provide a basis for PI as
well as further instrumentation. This may not be an
issue at the present but I don't think it is too far
off.
-john
Actually you need to have another kind of semaphore based on a new kind of
wait-queue: Priority based. I.e. the task with the highest priority get
woken up first. Then on top of that you build your mutex.
I was planning to start to look at it and try to see if I could getI myself wonder whether Ingo is 1 or N people.
anything to work, but I must admit I haven't got much further than
just getting Igno's -U8.1 up running.
To get a mutex with priority inheritance add an element pointing to theA task holding several mutexes shouldn't be an issue.
current owner and a field where you store the owners original priority
which it has to be set back to when it relases the mutex (I am not sure
how this will work out if someone holds several mutexes!)