From: Christoph Lameter <clameter@sgi.com>
To: Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] x86: Reduce memory and intra-node effects with large count NR_CPUs fixup
Date: Fri, 18 Jan 2008 10:54:59 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0801181054180.30775@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <4790A29F.9000006@sgi.com>
On Fri, 18 Jan 2008, Mike Travis wrote:
> I hadn't considered doing 32-bit NUMA changes as I didn't know if the
> NR_CPUS count would really be increased for the 32-bit architecture.
> I have been trying though not to break it. ;-)
32bit NUMA is tricky because ZONE_NORMAL memory is only available on node
0. There have been thorny difficult to debug issues in the past...
--
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:[~2008-01-18 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 22:35 [PATCH 0/3] x86: Reduce memory and intra-node effects with large count NR_CPUs fixup travis
2008-01-17 22:35 ` [PATCH 1/3] x86: Change size of node ids from u8 to u16 fixup travis
2008-01-17 22:35 ` [PATCH 2/3] x86: Change NR_CPUS arrays in numa_64 fixup travis
2008-01-17 22:35 ` [PATCH 3/3] x86: Change bios_cpu_apicid to percpu data variable fixup travis
2008-01-17 22:42 ` [PATCH 0/3] x86: Reduce memory and intra-node effects with large count NR_CPUs fixup Mike Travis
2008-01-18 9:23 ` Ingo Molnar
2008-01-18 12:59 ` Mike Travis
2008-01-18 18:54 ` 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.0801181054180.30775@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=travis@sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).