Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 27 Feb 2002 06:02:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 27 Feb 2002 06:02:18 -0500 Received: from garrincha.netbank.com.br ([200.203.199.88]:20745 "HELO netbank.com.br") by vger.kernel.org with SMTP id ; Wed, 27 Feb 2002 06:02:12 -0500 Date: Wed, 27 Feb 2002 08:01:45 -0300 (BRT) From: Rik van Riel X-X-Sender: To: Cc: , "linux-kernel@vger.kernel.org" Subject: Re: 2.4.19-preX: What we really need: -AA patches finally in thetree In-Reply-To: <3C7CB28A.CAD095B5@TeraPort.de> 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 On Wed, 27 Feb 2002, Martin Knoblauch wrote: > > > Not to begin the flamewar, but no thanks. rmap-12f blows -aa away AFAIK > > > on this P200 w/ 64MB ram. > > > > rmap still sucks on large systems though. I'd love to see rmap > > in the main kernel, but it needs to get the scalability fixed first. > > The main problem seems to be pagemap_lru_lock ... Rik & crew > > know about this problem, but let's give them some time to fix it > > before rmap gets put into mainline .... > > just out of curiosity: where does "large systems" start in your > context? My guess it would start at about 4 or 8 CPUs. Systems which have a lot of pagetable overhead would also suffer with -rmap, until -rmap supports pte_highmem. regards, Rik -- "Linux holds advantages over the single-vendor commercial OS" -- Microsoft's "Competing with Linux" document 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/