[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1105161343120.4353@chino.kir.corp.google.com>
Date: Mon, 16 May 2011 13:46:06 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: CAI Qian <caiqian@...hat.com>
cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, avagin@...il.com,
Andrey Vagin <avagin@...nvz.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mel@....ul.ie>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Minchan Kim <minchan.kim@...il.com>,
Hugh Dickins <hughd@...gle.com>,
Oleg Nesterov <oleg@...hat.com>
Subject: Re: OOM Killer don't works at all if the system have >gigabytes
memory (was Re: [PATCH] mm: check zone->all_unreclaimable in
all_unreclaimable())
On Fri, 13 May 2011, CAI Qian wrote:
> I have had a chance to test this patch after applied this patch manually
> (dd not apply cleanly) on the top of mainline kernel. The test is still
> running because it is trying to kill tons of python processes instread
> of the parent. Isn't there a way for oom to be smart enough to do
> "killall python"?
Not without userspace doing that explicitly, the oom killer attempts to
only kill the most memory-hogging task to free memory. If you're test is
constantly forking new processes which allocate memory then the oom killer
will just keep killing those children anytime it is out of memory.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists