Priority inversion happens when a higher priority task is help blocked by a lesser priority task.
Suppose a system has a low priority task L, a high priority task H and few medium priority tasks. Now resource R has been locked by L and goes to sleep due to other medium priority tasks coming in. Since medium priority tasks does not need R, they can interrupt L. Now if H also need the same resource R, it has to wait until L is done with it. So H gets blocked. This is called priority inversion. -Dinesh Bansal On Mon, Jun 20, 2011 at 10:35 PM, ricky <moon.afr...@gmail.com> wrote: > In priority inversion the high priority process has to wait for the > low priority process. why can't it just preempt the low priority one > instead of waiting? Is it becoz it will jeopardize system stability > or something else? > > -- > You received this message because you are subscribed to the Google Groups > "Algorithm Geeks" group. > To post to this group, send email to algogeeks@googlegroups.com. > To unsubscribe from this group, send email to > algogeeks+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/algogeeks?hl=en. > > -- Dinesh Bansal The Law of Win says, "Let's not do it your way or my way; let's do it the best way." -- You received this message because you are subscribed to the Google Groups "Algorithm Geeks" group. To post to this group, send email to algogeeks@googlegroups.com. To unsubscribe from this group, send email to algogeeks+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/algogeeks?hl=en.