On Sun, 6 Jun 2010 15:34:44 -0700 (PDT) David Rientjes <rientjes@xxxxxxxxxx> wrote: > It is possible to remove the special pagefault oom handler It'd be useful to describe what services that handler provides and to then describe how these services are retained in the new version. > by simply oom > locking all system zones and then calling directly into out_of_memory(). > > All populated zones must have ZONE_OOM_LOCKED set, otherwise there is a > parallel oom killing in progress that will lead to eventual memory freeing > so it's not necessary to needlessly kill another task. Should that have read "otherwise if there is"? (the code comments actually clarify all this) > The context in > which the pagefault is allocating memory is unknown to the oom killer, so > this is done on a system-wide level. > > If a task has already been oom killed and hasn't fully exited yet, this > will be a no-op since select_bad_process() recognizes tasks across the > system with TIF_MEMDIE set. > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>