From patchwork Fri Aug 30 13:15:45 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Srivatsa S. Bhat" X-Patchwork-Id: 2852008 Return-Path: X-Original-To: patchwork-linux-pm@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork2.web.kernel.org (Postfix) with ESMTP id EBE44C0AB5 for ; Fri, 30 Aug 2013 13:20:08 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 550ED2050F for ; Fri, 30 Aug 2013 13:20:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F2B3220503 for ; Fri, 30 Aug 2013 13:20:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756089Ab3H3NTu (ORCPT ); Fri, 30 Aug 2013 09:19:50 -0400 Received: from e35.co.us.ibm.com ([32.97.110.153]:54955 "EHLO e35.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756017Ab3H3NTu (ORCPT ); Fri, 30 Aug 2013 09:19:50 -0400 Received: from /spool/local by e35.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 30 Aug 2013 07:19:49 -0600 Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e35.co.us.ibm.com (192.168.1.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 30 Aug 2013 07:19:46 -0600 Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id AC65D1FF0023; Fri, 30 Aug 2013 07:19:45 -0600 (MDT) Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r7UDJi7n090102; Fri, 30 Aug 2013 07:19:44 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r7UDJfaE006946; Fri, 30 Aug 2013 07:19:43 -0600 Received: from srivatsabhat.in.ibm.com ([9.79.248.196]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r7UDJVLY006179; Fri, 30 Aug 2013 07:19:33 -0600 From: "Srivatsa S. Bhat" Subject: [RFC PATCH v3 06/35] mm: Add helpers to retrieve node region and zone region for a given page To: akpm@linux-foundation.org, mgorman@suse.de, hannes@cmpxchg.org, tony.luck@intel.com, matthew.garrett@nebula.com, dave@sr71.net, riel@redhat.com, arjan@linux.intel.com, srinivas.pandruvada@linux.intel.com, willy@linux.intel.com, kamezawa.hiroyu@jp.fujitsu.com, lenb@kernel.org, rjw@sisk.pl Cc: gargankita@gmail.com, paulmck@linux.vnet.ibm.com, svaidy@linux.vnet.ibm.com, andi@firstfloor.org, isimatu.yasuaki@jp.fujitsu.com, santosh.shilimkar@ti.com, kosaki.motohiro@gmail.com, srivatsa.bhat@linux.vnet.ibm.com, linux-pm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Date: Fri, 30 Aug 2013 18:45:45 +0530 Message-ID: <20130830131542.4947.76970.stgit@srivatsabhat.in.ibm.com> In-Reply-To: <20130830131221.4947.99764.stgit@srivatsabhat.in.ibm.com> References: <20130830131221.4947.99764.stgit@srivatsabhat.in.ibm.com> User-Agent: StGIT/0.14.3 MIME-Version: 1.0 X-TM-AS-MML: No X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13083013-4834-0000-0000-00000A9949EC Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org X-Spam-Status: No, score=-9.0 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Given a page, we would like to have an efficient mechanism to find out the node memory region and the zone memory region to which it belongs. Since the node is assumed to be divided into equal-sized node memory regions, the node memory region can be obtained by simply right-shifting the page's pfn by 'MEM_REGION_SHIFT'. But finding the corresponding zone memory region's index in the zone is not that straight-forward. To have a O(1) algorithm to find it out, define a zone_region_idx[] array to store the zone memory region indices for every node memory region. To illustrate, consider the following example: |<----------------------Node---------------------->| __________________________________________________ | Node mem reg 0 | Node mem reg 1 | (Absolute region |________________________|_________________________| boundaries) __________________________________________________ | ZONE_DMA | ZONE_NORMAL | | | | |<--- ZMR 0 --->|<-ZMR0->|<-------- ZMR 1 -------->| |_______________|________|_________________________| In the above figure, Node mem region 0: ------------------ This region corresponds to the first zone mem region in ZONE_DMA and also the first zone mem region in ZONE_NORMAL. Hence its index array would look like this: node_regions[0].zone_region_idx[ZONE_DMA] == 0 node_regions[0].zone_region_idx[ZONE_NORMAL] == 0 Node mem region 1: ------------------ This region corresponds to the second zone mem region in ZONE_NORMAL. Hence its index array would look like this: node_regions[1].zone_region_idx[ZONE_NORMAL] == 1 Using this index array, we can quickly obtain the zone memory region to which a given page belongs. Signed-off-by: Srivatsa S. Bhat --- include/linux/mm.h | 24 ++++++++++++++++++++++++ include/linux/mmzone.h | 7 +++++++ mm/page_alloc.c | 1 + 3 files changed, 32 insertions(+) -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/include/linux/mm.h b/include/linux/mm.h index 18fdec4..52329d1 100644 --- a/include/linux/mm.h +++ b/include/linux/mm.h @@ -723,6 +723,30 @@ static inline struct zone *page_zone(const struct page *page) return &NODE_DATA(page_to_nid(page))->node_zones[page_zonenum(page)]; } +static inline int page_node_region_id(const struct page *page, + const pg_data_t *pgdat) +{ + return (page_to_pfn(page) - pgdat->node_start_pfn) >> MEM_REGION_SHIFT; +} + +/** + * Return the index of the zone memory region to which the page belongs. + * + * Given a page, find the absolute (node) memory region as well as the zone to + * which it belongs. Then find the region within the zone that corresponds to + * that node memory region, and return its index. + */ +static inline int page_zone_region_id(const struct page *page) +{ + pg_data_t *pgdat = NODE_DATA(page_to_nid(page)); + enum zone_type z_num = page_zonenum(page); + unsigned long node_region_idx; + + node_region_idx = page_node_region_id(page, pgdat); + + return pgdat->node_regions[node_region_idx].zone_region_idx[z_num]; +} + #ifdef SECTION_IN_PAGE_FLAGS static inline void set_page_section(struct page *page, unsigned long section) { diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h index 010ab5b..76d9ed2 100644 --- a/include/linux/mmzone.h +++ b/include/linux/mmzone.h @@ -726,6 +726,13 @@ struct node_mem_region { unsigned long end_pfn; unsigned long present_pages; unsigned long spanned_pages; + + /* + * A physical (node) region could be split across multiple zones. + * Store the indices of the corresponding regions of each such + * zone for this physical (node) region. + */ + int zone_region_idx[MAX_NR_ZONES]; struct pglist_data *pgdat; }; diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 05cedbb..8ffd47b 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -4877,6 +4877,7 @@ static void __meminit init_zone_memory_regions(struct pglist_data *pgdat) zone_region->present_pages = zone_region->spanned_pages - absent; + node_region->zone_region_idx[zone_idx(z)] = idx; idx++; }