From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752006AbYIWMcU (ORCPT ); Tue, 23 Sep 2008 08:32:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751202AbYIWMcM (ORCPT ); Tue, 23 Sep 2008 08:32:12 -0400 Received: from mx1.chubb.wattle.id.au ([128.177.28.167]:37772 "EHLO mx1.chubb.wattle.id.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750990AbYIWMcL (ORCPT ); Tue, 23 Sep 2008 08:32:11 -0400 X-Greylist: delayed 2243 seconds by postgrey-1.27 at vger.kernel.org; Tue, 23 Sep 2008 08:32:11 EDT Date: Tue, 23 Sep 2008 21:54:17 +1000 Message-ID: <87abdz84d2.wl%peter@chubb.wattle.id.au> From: peter@chubb.wattle.id.au To: Nick Piggin Cc: Benjamin Herrenschmidt , Jeremy Fitzhardinge , Linux Memory Management List , Linux Kernel list , Hugh Dickins Subject: Re: PTE access rules & abstraction In-Reply-To: <20080923095054.GA29951@wotan.suse.de> References: <1221846139.8077.25.camel@pasglop> <48D739B2.1050202@goop.org> <1222117551.12085.39.camel@pasglop> <20080923031037.GA11907@wotan.suse.de> <1222147886.12085.93.camel@pasglop> <48D88904.4030909@goop.org> <1222152572.12085.129.camel@pasglop> <20080923095054.GA29951@wotan.suse.de> User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 MULE XEmacs/21.4 (patch 21) (Educational Television) (i486-linux-gnu) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>>>> "Nick" == Nick Piggin writes: Nick> On Tue, Sep 23, 2008 at 04:49:32PM +1000, Benjamin Herrenschmidt Nick> wrote: >> > What is the complete set of primitives we need? I also noticed >> that a > number of the existing pagetable operations are used only >> once or twice > in the core code; I wonder if we really need such >> special cases, or > whether we can make each arch pte operation >> carry a bit more weight? >> >> Yes, that was some of my concern. It's getting close to having one >> API per call site :-) Nick> I don't think that is a huge problem as such... if there was Nick> lots of repeated uses of the API I'd also be concerned about mm/ Nick> code not being well factored :) Is it worth taking another look at the page-table abstraction layer that Darren Williams posted here last year? PeterC