From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail202.messagelabs.com (mail202.messagelabs.com [216.82.254.227]) by kanga.kvack.org (Postfix) with SMTP id F3AE36B007E for ; Wed, 10 Feb 2010 23:10:47 -0500 (EST) Message-ID: <4B73833D.5070008@redhat.com> Date: Wed, 10 Feb 2010 23:10:37 -0500 From: Rik van Riel MIME-Version: 1.0 Subject: Re: [patch 4/7 -mm] oom: badness heuristic rewrite References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: David Rientjes Cc: Andrew Morton , KAMEZAWA Hiroyuki , Nick Piggin , Andrea Arcangeli , Balbir Singh , Lubos Lunak , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: On 02/10/2010 11:32 AM, David Rientjes wrote: > OOM_ADJUST_MIN and OOM_ADJUST_MAX have been exported to userspace since > 2006 via include/linux/oom.h. This alters their values from -16 to -1000 > and from +15 to +1000, respectively. That seems like a bad idea. Google may have the luxury of being able to recompile all its in-house applications, but this will not be true for many other users of /proc//oom_adj > +/* > + * Tasks that fork a very large number of children with seperate address spaces > + * may be the result of a bug, user error, or a malicious application. The oom > + * killer assesses a penalty equaling It could also be the result of the system getting many client connections - think of overloaded mail, web or database servers. -- All rights reversed. -- 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: email@kvack.org