From: "Jan Beulich" <jbeulich@novell.com>
To: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>, <travis@sgi.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: CONFIG_NR_CPUS limit for 32-bit
Date: Fri, 22 Aug 2008 15:36:46 +0100 [thread overview]
Message-ID: <48AEEB1E.76E4.0078.0@novell.com> (raw)
Given that the fixmap area size depends on NR_CPUS and that it can't
possibly cover 4096 CPUs (its size would be beyond 200Mb if I put things
together correctly, whereas the vmalloc area [of which the fixmap area is
a sub-portion] by default is 128MB) I can't see how this new limit ought to
even boot on any system.
Therefore I wonder whether the range shouldn't be restricted for X86_32.
Jan
reply other threads:[~2008-08-22 14:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48AEEB1E.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®