Thread (55 messages) 55 messages, 8 authors, 2012-11-01

Re: zram OOM behavior

From: Minchan Kim <minchan@kernel.org>
Date: 2012-11-01 05:12:53

On Wed, Oct 31, 2012 at 09:38:47PM -0700, David Rientjes wrote:
On Thu, 1 Nov 2012, Minchan Kim wrote:
quoted
If mutiple threads are page faulting and try to allocate memory, then they
should go to oom path and they will reach following code.

        if (task->flags & PF_EXITING) {
               if (task == current)
                        return OOM_SCAN_SELECT;
No, OOM_SCAN_SELECT does not return immediately and kill that process; it 
only prefers to kill that process first iff the oom killer isn't deferred 
because it finds TIF_MEMDIE threads or other PF_EXITING threads other than 
current.  So if multiple processes are in the exit path with PF_EXITING 
and require additional memory then the oom killed may defer without 
killing anything.  That's what I suspect is happening in this case.
Indeed.
Thanks for correcting me, David.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
-- 
Kind regards,
Minchan Kim

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help