Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 8 Sep 2002 16:43:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 8 Sep 2002 16:43:37 -0400 Received: from bay-bridge.veritas.com ([143.127.3.10]:44398 "EHLO mtvmime02.veritas.com") by vger.kernel.org with ESMTP id ; Sun, 8 Sep 2002 16:43:36 -0400 Date: Sun, 8 Sep 2002 21:48:58 +0100 (BST) From: Hugh Dickins X-X-Sender: hugh@localhost.localdomain To: Andrew Morton cc: Alan Cox , "Martin J. Bligh" , William Lee Irwin III , Paolo Ciarrocchi , Subject: Re: LMbench2.0 results In-Reply-To: <3D7B9988.6B8CD04F@digeo.com> Message-ID: 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: 1062 Lines: 22 On Sun, 8 Sep 2002, Andrew Morton wrote: > > We need to find some way of making vm_enough_memory not call get_page_state > so often. One way of doing that might be to make get_page_state dump > its latest result into a global copy, and make vm_enough_memory() > only get_page_state once per N invokations. A speed/accuracy tradeoff there. Accuracy is not very important in that sysctl_overcommit_memory 0 case e.g. the swapper_space.nr_pages addition was brought in at a time when it was very necessary, but usually overestimates now (or last time I thought about it). The main thing to look out for is running the same memory grabber twice in quick succession: not nice if it succeeds the first time, but not the second, just because of some transient effect that its old pages are temporarily uncounted. Hugh - 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/