Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S129156AbRCZUQn>; Mon, 26 Mar 2001 15:16:43 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S129164AbRCZUQd>; Mon, 26 Mar 2001 15:16:33 -0500
Received: from perninha.conectiva.com.br ([200.250.58.156]:33804 "HELO
	postfix.conectiva.com.br") by vger.kernel.org with SMTP
	id <S129156AbRCZUQY>; Mon, 26 Mar 2001 15:16:24 -0500
Date: Mon, 26 Mar 2001 17:05:21 -0300 (BRST)
From: Rik van Riel <riel@conectiva.com.br>
To: James Antill <james@and.org>
Cc: Guest section DW <dwguest@win.tue.nl>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
        Stephen Clouse <stephenc@theiqgroup.com>,
        "Patrick O'Rourke" <orourke@missioncriticallinux.com>,
        linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Prevent OOM from killing init
In-Reply-To: <nn66gwnyhn.fsf@code.and.org>
Message-ID: <Pine.LNX.4.21.0103261704060.24763-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

On 26 Mar 2001, James Antill wrote:

>  If you want overcommit great, and I think it's a valid default
> ... but it'd be nice if I could say I don't want it for apps that
> aren't written using glib etc.

Agreed.  Jonathan Morton seems to be making progress in testing
and debugging the non-overcommit patch from some time ago. If
things turn out to be trivial enough I wouldn't be surprised if
we got to see the option of non-overcommit somewhere in future
2.4 and 2.5 kernels...

regards,

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/