From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Mel <mel@csn.ul.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documenation/vm/numa
Date: Sat, 20 Apr 2002 12:47:53 -0700 [thread overview]
Message-ID: <2948370542.1019306872@[10.10.2.3]> (raw)
In-Reply-To: <Pine.LNX.4.44.0204201703320.3995-100000@skynet>
> + node_start_paddr The starting physical address of the node. This doesn't
> + work really well as an unsigned long as it breaks for
> + ia32 with PAE for example. A more suitable solution would be
> + to record this as a Page Frame Number (pfn). This could be
> + trivially defined as (page_phys_addr >> PAGE\_SHIFT).
This looks fine.
> + Alternatively, it could be the struct page * index inside
> + mem_map.
But I'd just omit this last sentence ... that only works for machines
with a contig mem_map (not NUMA), and it's kind of an accidental
kludge that happens to work in some cases, not the proper definition
(what I originally posted was confusing).
I actually submitted a patch a couple of days ago to fix these to
a pfn instead. If that gets in, we can update the documentation then.
M.
prev parent reply other threads:[~2002-04-20 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 3:56 Mel
2002-04-19 5:18 ` Martin J. Bligh
2002-04-19 20:25 ` Eric W. Biederman
2002-04-19 21:37 ` Martin J. Bligh
2002-04-20 16:05 ` Mel
2002-04-20 19:47 ` Martin J. Bligh [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='2948370542.1019306872@[10.10.2.3]' \
--to=martin.bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
/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
all inboxes | Powered by JetHome®