From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030557AbVKPXAJ (ORCPT ); Wed, 16 Nov 2005 18:00:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030558AbVKPXAJ (ORCPT ); Wed, 16 Nov 2005 18:00:09 -0500 Received: from 41.150.104.212.access.eclipse.net.uk ([212.104.150.41]:56035 "EHLO pinky.shadowen.org") by vger.kernel.org with ESMTP id S1030557AbVKPXAH (ORCPT ); Wed, 16 Nov 2005 18:00:07 -0500 Date: Wed, 16 Nov 2005 22:59:53 +0000 To: Mike Kravetz Cc: Andy Whitcroft , Anton Blanchard , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: [PATCH 0/3] SPARSEMEM: pfn_to_nid implementation Message-ID: References: <20051115221003.GA2160@w-mikek2.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline InReply-To: <20051115221003.GA2160@w-mikek2.ibm.com> User-Agent: Mutt/1.5.9i From: Andy Whitcroft Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I have reviewed the uses of pfn_to_nid() in 2.6.14-mm2. The only user of the non-init pfn_to_nid is the one in check_pte_range(). So we simply need to profide a non-early pfn_to_nid() implementation for SPARSEMEM. Whilst reviewing these interfaces I found two alternative dependant interfaces which are not used. Following this message are three patches: kvaddr_to_nid-not-used-in-common-code: removes the unused interface kvaddr_to_nid(). pfn_to_pgdat-not-used-in-common-code: removes the unused interface pfn_to_pgdat(). sparse-provide-pfn_to_nid: provides pfn_to_nid() for SPARSEMEM. Note that this implmentation assumes the pfn has been validated prior to use. The only intree user of this call does this. We perhaps need to make this part of the signature for this function. Mike, how does this look to you? -apw