:>
:>
:> To get a priority inversion like this one needs at least three tasks
:> with different priorities.
:
:Ah, yes. I stand corrected :)
:
:Thanks,
:-jj
Right, you need three tasks, but one of them has absolutely nothing to
do with the process holding the resource or the processin
> Almost, but not quite. In your scenario the low-priority task would
> get to run since the high-priority task is blocked and would thus
> eventually release the resource. No deadlock, no problem.
>
> The classic priority inversion that I have heard about is the following
> scenario:
>
> Three
On Thu, Apr 25, 2002 at 03:31:21PM -0700, JJ Behrens wrote:
> Dear Sir,
>
> > The classic priority inversion problem occurs when you have a low
> > priority process blocked on I/O and a higher priority process
> > monopolizing the cpu. Even though the lower priority process is
> >
