From: Christoph Lameter <christoph@engr.sgi.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-mm@kvack.org, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [RFC] Could we get rid of zone_table?
Date: Tue, 12 Sep 2006 10:41:07 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0609121037420.11278@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1158081512.9141.10.camel@localhost.localdomain>
On Tue, 12 Sep 2006, Dave Hansen wrote:
> On Mon, 2006-09-11 at 17:17 -0700, Christoph Lameter wrote:
> > I think the only case where we cannot encode the node number
> > are the early 32 bit NUMA systems? In that case one would only
> > need an array that maps the sections to the corresponding pgdat
> > structure and would then get to the zone from there. Dave, could
> > you add something like that to sparse.c?
>
> It can certainly be done. However, I'd rather keep it out of the actual
> struct mem_section, mostly because anything we do will be for a
> relatively rare, and relatively obsolete set of platforms.
There will be no zone table for UP and SMP. In !NUMA case NODE_DATA(0)
points to the pgdat with an exact replica of zone_table in the node_zones
field.
> Any new structure (or any mem_section additions) will just shift the
> exact same work that we're doing today with zone_table[] somewhere else.
> The impact into page_alloc.c is also pretty minimal. It is a single
> #ifdef, over a structure and a single function, right?
The problem is that zone_table seems to be useless except for
a very rare breed of early 32 bit IBM NUMA machines. Should not be in
page_alloc.c as far as I can tell.
--
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>
prev parent reply other threads:[~2006-09-12 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 0:17 Christoph Lameter
2006-09-12 17:18 ` Dave Hansen
2006-09-12 17:41 ` Christoph Lameter [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=Pine.LNX.4.64.0609121037420.11278@schroedinger.engr.sgi.com \
--to=christoph@engr.sgi.com \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.com \
--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