Priority Inheritance: The Real Story
Jul 16, 2002 — by LinuxDevices Staff — from the LinuxDevices Archive — viewsIn this guest editorial, TimeSys VP of Technology Doug Locke offers a rebuttal to Victor Yodaiken's recently published whitepaper on what's wrong with using a technique called 'priority inheritance' to avoid a problem in real-time systems known as 'priority inversion'. (Priority inversion is what caused big problems for the Mars Pathfinder Rover. It refers to the situation when a scheduled task must wait for a lower priority task to complete.) Locke writes . . .
“The technical arguments in [Yodaiken's] paper are not new, are generally correct, and have been widely discussed in the real-time research community for many years. However, the conclusions drawn in the paper are badly flawed.”
“Yodaiken's conclusions are drawn using the classic 'strawman' approach; the paper constructs an artificial hypothesis, and then shows that it might be dangerous. In this case his hypothesis is that priority inheritance is blindly used by engineers as a panacea for all priority inversion problems, and, because it has drawbacks under certain conditions, it is therefore dangerous and should never be used. In other words, because some carpenters might unsafely use a screwdriver to drive nails, screwdrivers should never be used . . .”
This article was originally published on LinuxDevices.com and has been donated to the open source community by QuinStreet Inc. Please visit LinuxToday.com for up-to-date news and articles about Linux and open source.