Marcelo Tosatti: Linux 2.4.23-pre5

En ugy emlekszem, hogy nem arrol volt szo, hogy teljesen eltunik az OOM killer, hanem arrol, hogy a current OOM killert eltavolitja AA es helyett a sajat OOM killer-et hasznalja. Szerinte ez sem az igazi OOM killer, mindenesetre szerinte jobb mint current, mert ez legalabb nem DoS-olja le a szervereket. Egeszen addig lesz ez a megoldas, amig egy jobb algoritmust nem ir o vagy mas.

"I've an algorithm that will work, and that will provide very good guarantees to kill the "best" task to make the machine usable again, with the needed protection against the security DoSes, but it's in no-way similar to the current oom killer."

"This oom killer on desktops may do a worse selections of the task to kill (the usual ssh now has a chance to be killed), but it fixes the oom deadlocks and it won't do stupid things on servers shall a netscape or whatever else app hit an userspace bug. So I've to prefer it, until I will write a reliable algorithm for the oom killing that won't fall into dosable corner cases so easily (mlock/nfs/database as the three most

common examples of where current mainline can fail, btw the lowmem shortage is another very common DoS that the oom killer will never notice, my tree doesn't deadlock [or at least not technically, in practice it may look like a kernel deadlock despite syscalls returns -ENOMEM ;) ] during lowmem shortage on the 64G boxes)."