Non-Deathmatch: Preempt v. Low-Latency Patch 178
LiquidPC writes: "In this whitepaper on Linux Scheduler Latency, Clark Williams of Red Hat compares the performance of two popular ways to improve kernel Linux preemption latency -- the preemption patch pioneered by MontaVista and the low-latency patch pioneered by Ingo Molnar -- and discovers that the best approach might be a combination of both."
co-op! (Score:2, Funny)
Oooooh (Score:4, Funny)
Interrupt priorities (Score:4, Funny)
Clearly, most RTOS designers have their priorities backwards.
Mmmm, donuts.
Re:One good way to reduce kernel latency.. (Score:4, Funny)
Honestly, I'm not trying to troll you here, but why would you WANT to run a *nix kernel on hardware that's responsible for engine timing? Especially when you apparently already have tech that works. Is the idea just to make vehicles that much harder for people to maintain? The day my mechanic keeps a sysadmin on duty so he patch my buggy Linux 4.5.3 ECU is the day I put a gun to my head and pull the trigger.
Aside from that. Way to inform the masses.
Re:I did better (Score:3, Funny)
la... (Score:2, Funny)
Re:One good way to reduce kernel latency.. (Score:2, Funny)
Low-latency and Preemptible on my Notebook (Score:3, Funny)
Worst of both worlds (Score:1, Funny)
Re:No argument here, move along. (Score:3, Funny)
They are both wrong. The correct solution is to remodulate the preemption and vent the latency through the Bussard collectors.
-
Re:Oooooh (Score:3, Funny)
Re:One good way to reduce kernel latency.. (Score:2, Funny)
If you use an early development kernel in a production engine, you deserve what you get.