I may miss something, but Ingo's initial low latency patch, did just
the schedule checks in the uaccess macros, but that was not enough to
cover all cases and ensure flat latency diagrams under all kinds of load.
So I am curious if the "we don't do it anywhere else" thing is possible
in practice, without requiring a radical change within the kernel.
Question: From a pure overhead point of view: does the preemption-points
approach score better (how much) than other approaches (eg pre-emptable kernel)
?
Benno.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/