public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH] remove zone_mem_map [3/4] pfn_to_page()
Date: Wed, 01 Feb 2006 13:34:38 +0000	[thread overview]
Message-ID: <43E0B8EE.7050306@shadowen.org> (raw)
In-Reply-To: <43E04206.8030104@mbligh.org>

Martin J. Bligh wrote:
> KAMEZAWA Hiroyuki wrote:
> 
>> Replace page_to_pfn() functions which uses zone->zone_mem_map.
>>
>> Although pfn_to_page() uses node->node_mem_map, page_to_pfn() uses
>> zone->zone_mem_map. I don't know why. This patch make page_to_pfn
>> use node->node_mem_map
> 
> 
> I think that might have been because it's a faster op, at least on
> some architectures, under sparsemem. Andy, can you confirm / deny?
> Some part of the mapping was embedded in the page flags.
> 
> If Andy can't recall, I'll look again on Thursday when I'm back ...

Not for SPARSEMEM anyhow, we don't use any of those pointers we are
using the per section maps based on pfn.  However, I would assume we
have it as an optimisation for the FLAT/DISCONTIG forms -- as we have a
quick lookup of the zone.  That said we should have a quick lookup of
the node too and it looks like the proposed replacement is using that
one.  So I'd say this should be about as performant.

-apw

--
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>

      parent reply	other threads:[~2006-02-01 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01  3:27 [RFC][PATCH] remove zone_mem_map [3/4] pfn_to_page() KAMEZAWA Hiroyuki
2006-02-01  5:07 ` Martin J. Bligh
2006-02-01  5:21   ` KAMEZAWA Hiroyuki
2006-02-01 13:34   ` Andy Whitcroft [this message]

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=43E0B8EE.7050306@shadowen.org \
    --to=apw@shadowen.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@mbligh.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