Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 17 Jul 2002 15:38:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 17 Jul 2002 15:38:13 -0400 Received: from garrincha.netbank.com.br ([200.203.199.88]:50954 "HELO garrincha.netbank.com.br") by vger.kernel.org with SMTP id ; Wed, 17 Jul 2002 15:38:13 -0400 Date: Wed, 17 Jul 2002 16:41:01 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Daniel Phillips cc: Andrew Morton , Linus Torvalds , lkml Subject: Re: [patch 1/13] minimal rmap In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org 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: 1285 Lines: 35 On Wed, 17 Jul 2002, Daniel Phillips wrote: > On Wednesday 17 July 2002 21:31, Rik van Riel wrote: > > On Wed, 17 Jul 2002, Daniel Phillips wrote: > > > On Wednesday 17 July 2002 07:29, Andrew Morton wrote: > > > > 11: The nightly updatedb run is still evicting everything. > > > > > > That is not a problem with rmap per se, it's a result of not properly > > > handling streaming IO. > > > > Umm, updatedb isn't exactly streaming... > > You're right, it's not exactly, it's hitting every directory entry on ^^^^^^^^^^^^^^^ > the system, hopefully just once. Let's not call it streaming, let's > call it... err... use-once? ;-) Nope. If it hits every directory entry once, it'll hit every page with directory or inode information multiple times, causing that page to enter the active list and push out process pages. This is exactly what we want to prevent. regards, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ - 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/