Currently ALL holders are boosted to the priority of the highest priority waiter.Yes and No. For counting semaphores we have multiple holders for example with priorities 10, 50 and 90. Now a task with priority 100 comes and wants to take a semaphore. Priority which of the holders should be increased? The lowest or the highest holder? With a real-time point of view it should be 90 boosted to 100, but is the current implementation doing that?
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt
- Development priorities (was: [Breaking change]... Nathan Hartman
- Re: Development priorities (was: [Breaking... Tomek CEDRO
- Re:Re: [Breaking change] Move nxmutex to sched 奇诺
- Re: [Breaking change] Move nxmutex to sched David S. Alessio
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt
- Re: [Breaking change] Move nxmutex to sched Tomek CEDRO
- Re: [Breaking change] Move nxmutex to sche... Petro Karashchenko
- Re: [Breaking change] Move nxmutex to ... Gregory Nutt
- Re: [Breaking change] Move nxmutex to ... Petro Karashchenko
- Re: [Breaking change] Move nxmutex to ... Gregory Nutt
- Re: [Breaking change] Move nxmutex to ... Petro Karashchenko
- Re: [Breaking change] Move nxmutex to ... Gregory Nutt
- Re: [Breaking change] Move nxmutex to ... Petro Karashchenko
- Re: [Breaking change] Move nxmutex to ... Petro Karashchenko
- Re: [Breaking change] Move nxmutex to ... Gregory Nutt
- Re: [Breaking change] Move nxmutex to ... Gregory Nutt
- Re: [Breaking change] Move nxmutex to ... Xiang Xiao
- Re: [Breaking change] Move nxmutex to ... Xiang Xiao
- Re: [Breaking change] Move nxmutex to ... Petro Karashchenko
- Re: [Breaking change] Move nxmutex to ... Xiang Xiao