Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 7 Dec 2001 00:35:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 7 Dec 2001 00:35:46 -0500 Received: from www.wen-online.de ([212.223.88.39]:52742 "EHLO wen-online.de") by vger.kernel.org with ESMTP id ; Fri, 7 Dec 2001 00:35:28 -0500 Date: Fri, 7 Dec 2001 06:37:07 +0100 (CET) From: Mike Galbraith X-X-Sender: To: Alan Cox cc: Rik van Riel , Roy Sigurd Karlsbakk , Pablo Borges , Subject: Re: Kernel 2.4.16 & Heavy I/O 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 Thu, 6 Dec 2001, Alan Cox wrote: > > Once a page is used twice, it's not a candidate for eviction > > until (most of) the use-once pages are gone. > > > > This means that if you have these 40 MB of used-twice-but-never-again > > buffer cache memory, this memory will never be evicted until other > > pages get promoted from use-once to active. > > Its worth noting btw that you can intentionally exploit this in an app > to get unfair use of memory. That makes me very dubious about the heuristic In Rik's VM I had a problem with use-once when Bonnie was doing rewrite. It's used-twice data became too hard to get rid of at the aging volume we were doing, leading to an inactive shortage and unwanted swapping. The active list grew until ~all of ram was on the active list. I 'fixed' it here by keeping the dirty list very strictly ordered (lengthened it too) and requiring more than two accesses before promoting to active. I have not seen this behavior in the new VM yet. -Mike - 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/