Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 11 Sep 2002 17:39:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 11 Sep 2002 17:39:26 -0400 Received: from pc1-cwma1-5-cust128.swa.cable.ntl.com ([80.5.120.128]:18173 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Wed, 11 Sep 2002 17:39:25 -0400 Subject: Re: Killing/balancing processes when overcommited From: Alan Cox To: Jim Sibley Cc: linux-kernel@vger.kernel.org, riel@conectiva.com.br, ltc@linux.ibm.com, Troy Reed In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-7) Date: 11 Sep 2002 22:44:24 +0100 Message-Id: <1031780664.2994.21.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 810 Lines: 16 On Wed, 2002-09-11 at 19:08, Jim Sibley wrote: > I have run into a situation in a multi-user Linux environment that when > memory is exhausted, random things happen. The best case is that the > "offending" user's task is killed. Just as likely, another user's task is The best case is that you don't allow overcommit. 2.4 supports that in the Red Hat and -ac trees. Robert Love forward ported the changes to 2.5.x. There is an outstanding need to add an additional "root factor" so root can get some memory other people cannot, but otherwise it seems to work well - 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/