From: Dave Hansen <haveblue@us.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andy Whitcroft <apw@shadowen.org>, linux-mm@kvack.org
Subject: Re: [PATCH] Get rid of zone_table
Date: Wed, 13 Sep 2006 14:58:55 -0700 [thread overview]
Message-ID: <1158184735.9141.167.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0609131452330.19506@schroedinger.engr.sgi.com>
On Wed, 2006-09-13 at 14:54 -0700, Christoph Lameter wrote:
> On Wed, 13 Sep 2006, Dave Hansen wrote:
> > Now that I think about it, we should have room to encode that thing
> > inside of the section number on 32-bit platforms.
>
> We already have 1k nodes on IA64 and you can expect 16k in the
> near future. I think you need at least 16 bit.
>
> Sorry I am a bit new to sparsemem but it seems that the mem sections are
> arrays of pointers. You would like to store the node number in the lower
> unused bits?
I thought this patch was only for 32-bit NUMA platforms that have run
out of bits in page->flags to encode the data. Does it apply to ia64 as
well somehow?
-- Dave
--
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>
next prev parent reply other threads:[~2006-09-13 21:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 20:44 Christoph Lameter
2006-09-13 20:53 ` Dave Hansen
2006-09-13 21:40 ` Christoph Lameter
2006-09-13 21:47 ` Dave Hansen
2006-09-13 21:54 ` Christoph Lameter
2006-09-13 21:58 ` Dave Hansen [this message]
2006-09-13 22:02 ` Christoph Lameter
2006-09-15 13:28 ` Andy Whitcroft
2006-09-15 16:32 ` Dave Hansen
2006-09-15 17:13 ` Christoph Lameter
2006-09-15 17:51 ` Christoph Lameter
2006-09-14 10:33 ` Andy Whitcroft
2006-09-14 21:46 ` Christoph Lameter
2006-09-15 13:07 ` Andy Whitcroft
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=1158184735.9141.167.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=apw@shadowen.org \
--cc=clameter@sgi.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