Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 25 Feb 2003 17:04:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 25 Feb 2003 17:04:43 -0500 Received: from [195.223.140.107] ([195.223.140.107]:135 "EHLO athlon.random") by vger.kernel.org with ESMTP id ; Tue, 25 Feb 2003 17:04:41 -0500 Date: Tue, 25 Feb 2003 23:16:02 +0100 From: Andrea Arcangeli To: "Martin J. Bligh" Cc: William Lee Irwin III , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: Minutes from Feb 21 LSE Call Message-ID: <20030225221602.GZ29467@dualathlon.random> References: <20030225171727.GN29467@dualathlon.random> <20030225174359.GA10411@holomorphy.com> <20030225175928.GP29467@dualathlon.random> <20030225185008.GF10396@holomorphy.com> <20030225191817.GT29467@dualathlon.random> <372680000.1046201260@flay> <20030225203001.GV29467@dualathlon.random> <417110000.1046206424@flay> <20030225211718.GY29467@dualathlon.random> <421460000.1046207575@flay> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <421460000.1046207575@flay> User-Agent: Mutt/1.4i X-GPG-Key: 1024D/68B9CB43 X-PGP-Key: 1024R/CB4660B9 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1487 Lines: 29 On Tue, Feb 25, 2003 at 01:12:55PM -0800, Martin J. Bligh wrote: > >> Because you don't set up and tear down the rmap pte-chains for every > >> fault in / delete of any page ... it just works off the vmas. > > > > so basically it uses the rmap that we always had since at least 2.2 for > > everything but anon mappings, right? this is what DaveM did a few years > > back too. This makes lots of sense to me, so at least we avoid the > > duplication of rmap information, even if it won't fix the anonymous page > > overhead, but clearly it's much lower cost for everything but anonymous > > pages. > > Right ... and anonymous chains are about 95% single-reference (at least for > the case I looked at), so they're direct mapped from the struct page with > no chain at all. Cuts out something like 95% of the space overhead of > pte-chains, and 65% of the time (for kernel compile -j256 on 16x system). > However, it's going to be a little more expensive to *use* the mappings, > so we need to measure that carefully. Sure, it is more expensive to use them, but all we care about is complexity, and they solve the complexity problem just fine, so I definitely prefer it. Cpu utilization during heavy swapping isn't a big deal IMHO Andrea - 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/