Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 11 Dec 2001 13:01:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 11 Dec 2001 13:01:48 -0500 Received: from perninha.conectiva.com.br ([200.250.58.156]:8977 "HELO perninha.conectiva.com.br") by vger.kernel.org with SMTP id ; Tue, 11 Dec 2001 13:01:38 -0500 Date: Tue, 11 Dec 2001 14:45:16 -0200 (BRST) From: Marcelo Tosatti To: Rik van Riel Cc: Andrew Morton , Andrea Arcangeli , lkml Subject: Re: 2.4.16 & OOM killer screw up (fwd) In-Reply-To: Message-ID: 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 Mon, 10 Dec 2001, Rik van Riel wrote: > On Mon, 10 Dec 2001, Andrew Morton wrote: > > > A fix may be to just remove the use-once stuff. It is one of the > > sources of this problem, because it's overpopulating the inactive list. > > Absolutely. Use-once is an inherently unstable system, suitable > for things like a database load (where you know you want to spend > a certain percentage of your RAM on caching the index), but not > suitable for a general-purpose VM, where you have no idea how > large the working set will be. > > I'll take a stab at completely removing the use-once stuff as an > emergency measure. Rik, Could you please make a patch without use-once and post the patch to lkml ? This way people can test it and report performance results. I really would prefer to remove use-once as I also think its an optimization which breaks some workloads, but I want to know what happens in practice if we do that. - 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/