From: "H. Peter Anvin" <hpa@zytor.com>
To: Josh Boyer <jwboyer@redhat.com>, Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
prarit@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Allow NR_CPUS=1024
Date: Sun, 03 Nov 2013 09:43:36 -0800 [thread overview]
Message-ID: <52768B48.5030408@zytor.com> (raw)
In-Reply-To: <20131103155729.GB9944@hansolo.jdub.homelinux.org>
On 11/03/2013 07:57 AM, Josh Boyer wrote:
>
> OK, that makes sense. So in this scenario, we could probably either:
>
> a) do away with MAXSMP entirely and just depend on
> CONFIG_CPUMASK_OFFSTACK.
>
> b) make MAXSMP something even higher than 4096. Like 5120 or 6144, etc.
>
> Which would you prefer? Either is easy enough to code up, I just need
> to know which I should shoot for.
>
Let's get rid of MAXSMP.
-hpa
next prev parent reply other threads:[~2013-11-03 17:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 14:11 [PATCH] x86: Allow NR_CPUS=1024 Josh Boyer
2013-11-03 10:18 ` Ingo Molnar
2013-11-03 10:21 ` Ingo Molnar
2013-11-03 15:57 ` Josh Boyer
2013-11-03 17:43 ` H. Peter Anvin [this message]
2013-11-04 6:51 ` Ingo Molnar
2013-11-04 16:31 ` H. Peter Anvin
2013-11-04 6:53 ` Ingo Molnar
2013-11-04 14:01 ` Josh Boyer
2013-11-04 14:10 ` Ingo Molnar
2013-11-04 14:16 ` Josh Boyer
2013-11-04 14:54 ` Prarit Bhargava
2013-11-04 15:56 ` Russ Anderson
2013-11-04 17:48 ` Ingo Molnar
2013-11-04 19:08 ` H. Peter Anvin
2013-11-04 20:11 ` Ingo Molnar
2013-11-04 22:50 ` H. Peter Anvin
2013-11-05 6:25 ` Ingo Molnar
2013-11-05 6:31 ` Li Zefan
2013-11-03 14:29 ` Prarit Bhargava
2013-11-03 14:42 ` Russ Anderson
2013-11-05 14:37 ` [PATCH 1/2 v2] x86: Allow higher NR_CPUS values Josh Boyer
2013-11-05 14:38 ` [PATCH 2/2] x86: Increase MAXSMP CPU count to 8192 Josh Boyer
2013-11-06 5:56 ` [PATCH v2 " Ingo Molnar
2013-11-06 14:10 ` Josh Boyer
2013-11-06 11:20 ` [tip:x86/cpu] x86/cpu: Increase max " tip-bot for Josh Boyer
2013-11-06 7:15 ` [PATCH 1/2 v2] x86: Allow higher NR_CPUS values Ingo Molnar
2013-11-06 14:12 ` Josh Boyer
2013-11-06 15:04 ` Josh Boyer
2013-11-06 15:21 ` [PATCH v3] x86/cpu: " Josh Boyer
2013-11-07 9:15 ` Ingo Molnar
2013-11-07 13:51 ` Josh Boyer
2013-11-06 11:20 ` [tip:x86/cpu] " tip-bot for Josh Boyer
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=52768B48.5030408@zytor.com \
--to=hpa@zytor.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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