Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id <S132152AbRC1AyO>; Tue, 27 Mar 2001 19:54:14 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id <S132188AbRC1AyE>; Tue, 27 Mar 2001 19:54:04 -0500
Received: from 3-123.cwb-adsl.telepar.net.br ([200.193.162.123]:6673 "EHLO imladris.rielhome.conectiva") by vger.kernel.org with ESMTP id <S132152AbRC1Axv>; Tue, 27 Mar 2001 19:53:51 -0500
Date: Tue, 27 Mar 2001 21:52:49 -0300 (BRST)
From: Rik van Riel <riel@conectiva.com.br>
To: james <jdickens@ameritech.net>
cc: linux-kernel@vger.kernel.org
Subject: Re: Ideas for the oom problem
In-Reply-To: <01032718343500.32154@friz.themagicbus.com>
Message-ID: <Pine.LNX.4.21.0103272151580.8261-100000@imladris.rielhome.conectiva>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 675
Lines: 22

On Tue, 27 Mar 2001, james wrote:

> Here are my ideas on how too deal with the oom situation,

> I propose a three prong approach too this problem

Isn't that a bit much for an emergency situation that never
even occurs on most systems ?

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

		http://www.surriel.com/
http://www.conectiva.com/	http://distro.conectiva.com.br/

-
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/