From: Andy Whitcroft <apw@shadowen.org>
To: mike kravetz <kravetz@us.ibm.com>
Cc: Michael Ellerman <michael@ellerman.id.au>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, haveblue@us.ibm.com
Subject: Re: [PATCH] SPARSEMEM + NUMA can't handle unaligned memory regions?
Date: Tue, 09 May 2006 17:14:30 +0100 [thread overview]
Message-ID: <4460BFE6.4060504@shadowen.org> (raw)
In-Reply-To: <20060509160528.GA3168@w-mikek2.ibm.com>
mike kravetz wrote:
> On Tue, May 09, 2006 at 02:34:51PM +0100, Andy Whitcroft wrote:
>
>>3) record the nid -- when we record the memory present in the system we
>>are passed the nid.
>>
>>Somehow the last of these seems the most logical given we have the
>>correct information at the time we record that we need to instantiate
>>the section. So I had a quick go at something which seems to have come
>>out pretty clean. Attached is a completly untested patch to show what I
>>am proposing.
>
>
> Looks sane to me. I've always wanted to encode the nid in the section.
> But, never had a compelling reason to do so.
>
> With this code in place, we could optimize the pfn_to_nid() routines to
> now obtain the nid from the section (rather than page struct). However,
> I'm not sure this is worth the effort.
Well its only in there temporarily during init, its not in there once we
have allocated the section mem_map.
-apw
prev parent reply other threads:[~2006-05-09 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 7:03 Michael Ellerman
2006-05-09 8:32 ` Andy Whitcroft
2006-05-09 9:11 ` Michael Ellerman
2006-05-09 10:24 ` Andy Whitcroft
2006-05-09 13:34 ` Andy Whitcroft
2006-05-09 14:28 ` Andy Whitcroft
2006-05-09 16:26 ` Dave Hansen
2006-05-09 16:31 ` Andy Whitcroft
2006-05-10 6:06 ` Michael Ellerman
2006-05-10 10:51 ` [PATCH] sparsemem record nid during memory present Andy Whitcroft
2006-05-09 16:05 ` [PATCH] SPARSEMEM + NUMA can't handle unaligned memory regions? mike kravetz
2006-05-09 16:14 ` 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=4460BFE6.4060504@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
/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
Powered by JetHome