From: William Lee Irwin III <wli@holomorphy.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Discontig-devel] [PATCH] another discontig patch
Date: Mon, 23 Jun 2003 17:20:44 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105638893811288@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105618641519753@msgid-missing>
At some point in the past, someone wrote:
>># define pfn_to_page(pfn) (vmem_map + (pfn))
>># define page_to_pfn(page) ((unsigned long) (page - vmem_map))
On Sat, Jun 21, 2003 at 07:48:08AM -0700, Martin J. Bligh wrote:
> I really don't see how you *can't* do that, and have it still work.
> If the mem_map is placed in node local memory, and not a size that
> happens to be a complete number of pages, even if you pack it down
> into a vmem_map, it's still not contiguous. So adding a pfn (physical
> page frame number) to the base of vmem_map can NOT give you the correct
> address.
> Presumably this *is* working for you ... but I'm buggered if I know how ;-)
> Maybe I just need more coffee ;-)
It's a sparse array. The interstices between nodes are padded with
empty virtualspace in order to cheapen the indexing operation. i.e. the
nodes' local mem_map's are virtually positioned according to the range
of pfns they span. If 32-bit weren't as pressed for virtualspace it
could do likewise.
-- wli
next prev parent reply other threads:[~2003-06-23 17:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 9:06 [Discontig-devel] [PATCH] another discontig patch Christoph Hellwig
2003-06-21 14:48 ` Martin J. Bligh
2003-06-22 5:53 ` Jesse Barnes
2003-06-22 5:57 ` Jesse Barnes
2003-06-22 15:25 ` Martin J. Bligh
2003-06-23 17:20 ` William Lee Irwin III [this message]
2003-07-16 19:29 ` Jesse Barnes
2003-07-16 19:40 ` Matthew Wilcox
2003-07-16 19:51 ` Jesse Barnes
2003-07-16 19:56 ` Erich Focht
2003-07-16 22:37 ` Jesse Barnes
2003-07-17 8:23 ` Erich Focht
2003-07-18 0:16 ` Jesse Barnes
2003-07-18 16:15 ` Erich Focht
2003-07-21 18:46 ` Takayoshi Kochi
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=marc-linux-ia64-105638893811288@msgid-missing \
--to=wli@holomorphy.com \
--cc=linux-ia64@vger.kernel.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