Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932174AbVIGQrD (ORCPT ); Wed, 7 Sep 2005 12:47:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932177AbVIGQrD (ORCPT ); Wed, 7 Sep 2005 12:47:03 -0400 Received: from omx2-ext.sgi.com ([192.48.171.19]:5297 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S932174AbVIGQrB (ORCPT ); Wed, 7 Sep 2005 12:47:01 -0400 Date: Wed, 7 Sep 2005 08:42:22 -0700 (PDT) From: Christoph Lameter To: "Martin J. Bligh" cc: torvalds@osdl.org, akpm@osdl.org, nickpiggin@yahoo.com.au, hugh@veritas.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: Hugh's alternate page fault scalability approach on 512p Altix In-Reply-To: <20660000.1126103324@[10.10.2.4]> Message-ID: References: <20660000.1126103324@[10.10.2.4]> 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: 1164 Lines: 29 On Wed, 7 Sep 2005, Martin J. Bligh wrote: > > Anticipatory prefaulting raises the highest fault rate obtainable three-fold > > through gang scheduling faults but may allocate some pages to a task that are > > not needed. > > IIRC that costed more than it saved, at least for forky workloads like a > kernel compile - extra cost in zap_pte_range etc. If things have changed > substantially in that path, I guess we could run the numbers again - has > been a couple of years. Right. The costs come about through wrong anticipations installing useless mappings. The patches that I posted have this feature off by default. Gang scheduling can be enabled by modifying a value in /proc. But I guess the approach is essentially dead unless others want this feature too. The current page fault scalability approach should be fine for a couple of years and who knows what direction mmu technology has taken then. - 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/