From: Christoph Lameter <clameter@engr.sgi.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Dave Hansen <haveblue@us.ibm.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] remove zone_mem_map
Date: Tue, 21 Feb 2006 19:04:27 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602211900450.23557@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <43FBAEBA.2020300@jp.fujitsu.com>
On Wed, 22 Feb 2006, KAMEZAWA Hiroyuki wrote:
> This patch removes zone_mem_map.
Note that IA64 does not seem to depend on zone_mem_map...
> Index: test/include/asm-generic/memory_model.h
> ===================================================================
> --- test.orig/include/asm-generic/memory_model.h
> +++ test/include/asm-generic/memory_model.h
> @@ -47,9 +47,9 @@ extern unsigned long page_to_pfn(struct
>
> #define page_to_pfn(pg) \
> ({ struct page *__pg = (pg); \
> - struct zone *__zone = page_zone(__pg); \
> - (unsigned long)(__pg - __zone->zone_mem_map) + \
> - __zone->zone_start_pfn; \
> + struct pglist_data *__pgdat = NODE_DATA(page_to_nid(__pg)); \
> + (unsigned long)(__pg - __pgdat->node_mem_map) + \
> + __pgdat->node_start_pfn; \
> })
NODE_DATA is an arch specific lookup, If it always is a table lookup
then the performance will be comparable to page_zone because that also
involves one table lookup.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-02-22 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 0:22 KAMEZAWA Hiroyuki
2006-02-22 2:33 ` Andrew Morton
2006-02-22 2:52 ` KAMEZAWA Hiroyuki
2006-02-22 3:04 ` Christoph Lameter [this message]
2006-02-22 3:25 ` KAMEZAWA Hiroyuki
2006-02-22 3:41 ` Christoph Lameter
2006-02-22 3:52 ` KAMEZAWA Hiroyuki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0602211900450.23557@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox