Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 23 Jan 2002 12:07:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 23 Jan 2002 12:07:39 -0500 Received: from dsl-213-023-038-076.arcor-ip.net ([213.23.38.76]:65433 "EHLO starship.berlin") by vger.kernel.org with ESMTP id ; Wed, 23 Jan 2002 12:07:36 -0500 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: "Duraid Madina" , Subject: Re: VM: Where do we stand? Date: Wed, 23 Jan 2002 18:12:26 +0100 X-Mailer: KMail [version 1.3.2] In-Reply-To: <000901c1a3f0$d2e44ba0$022a17ac@simplex> In-Reply-To: <000901c1a3f0$d2e44ba0$022a17ac@simplex> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On January 23, 2002 10:32 am, Duraid Madina wrote: > >The paging queues ( determing the age of the page and whether to > >free or clean it) need to be written... the algorithms being used > >are terrible. > > > > * For the nominal page scan, it is using a one-hand clock algorithm. > > All I can say is: Oh my god! Are they nuts? That was abandoned > > a decade ago. We don't use a one-hand clock now, we use an lru list coupled with a virtual scan which sucks slightly less, but only slightly. > > The priority mechanism they've implemented is nearly > > useless. There's a new priority mechanism now ;-) > > * To locate pages to swap out, it takes a pass through the task list. > > Ostensibly it locates the task with the largest RSS to then try to > > swap pages out from rather then select pages that are not in use. > > From my read of the code, it also botches this badly. It now tries to select pages that are not in use. -- Daniel - 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/