From: Andi Kleen <andi@firstfloor.org>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: <mingo@elte.hu>, <tglx@linutronix.de>, <hpa@zytor.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH, resend] i386: also limit NODES_HIGH_SHIFT here
Date: Thu, 12 Mar 2009 14:29:37 +0100 [thread overview]
Message-ID: <87vdqeeuny.fsf@basil.nowhere.org> (raw)
In-Reply-To: <49B90F12.76E4.0078.0@novell.com> (Jan Beulich's message of "Thu, 12 Mar 2009 12:33:06 +0000")
"Jan Beulich" <jbeulich@novell.com> writes:
> Impact: configuration bug fix
>
> Just like for x86-64, the range of widths valid for NODE_SHIFT is not
> unbounded. The upper bound 64-bit uses is definitely also an upper
> bound for 32-bit.
I think that's actually obsolete, there's no real 128 nodes limit.
The only limit used to be 256 nodes because you can't have more nodes
than CPUs, but that's obsolete with x2apic.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-03-12 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 12:33 [PATCH, resend] i386: also limit NODES_HIGH_SHIFT here Jan Beulich
2009-03-12 13:29 ` Andi Kleen [this message]
2009-03-13 2:33 ` [tip:x86/mm] x86, 32-bit: " Jan Beulich
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=87vdqeeuny.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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