[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1108261106570.13943@chino.kir.corp.google.com>
Date: Fri, 26 Aug 2011 11:09:14 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Konstantin Khlebnikov <khlebnikov@...nvz.org>
cc: Michal Hocko <mhocko@...e.cz>, Oleg Nesterov <oleg@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [PATCH] oom: skip frozen tasks
On Fri, 26 Aug 2011, Konstantin Khlebnikov wrote:
> Maybe just fix this "panic" logic? OOM killer should panic only on global
> memory shortage.
>
NO, it shouldn't, we actually rely quite extensively on cpusets filled
with OOM_DISABLE threads to panic because the job scheduler would be
unresponsive in such a condition and it'd much better to panic and reboot
than to brick the machine. I'm not sure where you're getting all your
information from, but please don't pass it off as principles.
You can set the panic logic to be whatever you want with
/proc/sys/vm/panic_on_oom. See Documentation/filesystems/proc.txt for
more information.
--
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