On Fri, 18 Sep 2015, Oleg Nesterov wrote:
> To simplify the discussion lets ignore PF_FROZEN, this is another issue.
Ok.
Subject: Allow multiple kills from the OOM killer
The OOM killer currently aborts if it finds a process that already is having
access to the reserve memory pool for exit processing. This is done so that
the reserves are not overcommitted but on the other hand this also allows
only one process being oom killed at the time. That process may be stuck
in D state.
Signed-off-by: Christoph Lameter <cl@xxxxxxxxx>
Index: linux/mm/oom_kill.c
===================================================================
--- linux.orig/mm/oom_kill.c 2015-09-18 11:58:52.963946782 -0500
+++ linux/mm/oom_kill.c 2015-09-18 11:59:42.010684778 -0500
@@ -264,10 +264,9 @@ enum oom_scan_t oom_scan_process_thread(
* This task already has access to memory reserves and is being killed.
* Don't allow any other task to have access to the reserves.
*/
- if (test_tsk_thread_flag(task, TIF_MEMDIE)) {
- if (oc->order != -1)
- return OOM_SCAN_ABORT;
- }
+ if (test_tsk_thread_flag(task, TIF_MEMDIE))
+ return OOM_SCAN_CONTINUE;
+
if (!task->mm)
return OOM_SCAN_CONTINUE;
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>