Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753549Ab0A2QV1 (ORCPT ); Fri, 29 Jan 2010 11:21:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752523Ab0A2QVX (ORCPT ); Fri, 29 Jan 2010 11:21:23 -0500 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:54647 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752338Ab0A2QVU (ORCPT ); Fri, 29 Jan 2010 11:21:20 -0500 Date: Fri, 29 Jan 2010 16:21:37 +0000 From: Alan Cox To: "KAMEZAWA Hiroyuki" Cc: vedran.furac@gmail.com, "KAMEZAWA Hiroyuki" , "Andrew Morton" , "linux-mm@kvack.org" , rientjes@google.com, minchan.kim@gmail.com, "linux-kernel@vger.kernel.org" , "balbir@linux.vnet.ibm.com" Subject: Re: [PATCH v3] oom-kill: add lowmem usage aware oom kill handling Message-ID: <20100129162137.79b2a6d4@lxorguk.ukuu.org.uk> In-Reply-To: References: X-Mailer: Claws Mail 3.7.3 (GTK+ 2.18.5; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 662 Lines: 14 > panic_on_oom=1 works enough well.For Vedran's, overcommit memory will work > well. But oom-killer kills very bad process if not tweaked. > So, I think some improvement should be done. That is why we have the per process oom_adj values - because for nearly fifteen years someone comes along and says "actually in my environment the right choice is ..." Ultimately it is policy. The kernel simply can't read minds. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/