From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64, defconfig: Increase NR_CPUS default to 64
Date: Tue, 09 Sep 2014 11:28:07 +0200 [thread overview]
Message-ID: <1410254887.22255.14.camel@x220> (raw)
In-Reply-To: <20140909080740.GP23009@pengutronix.de>
On Tue, 2014-09-09 at 10:07 +0200, Uwe Kleine-K?nig wrote:
> On Mon, Sep 08, 2014 at 01:44:48PM +0200, Robert Richter wrote:
> > @@ -252,11 +252,11 @@ config SCHED_SMT
> > places. If unsure say N here.
> >
> > config NR_CPUS
> > - int "Maximum number of CPUs (2-32)"
> > - range 2 32
> > + int "Maximum number of CPUs (2-64)"
> > + range 2 64
> > depends on SMP
> > # These have to remain sorted largest to smallest
> Unrelated to the patch: What does this comment mean? There is only one
> line following, so it's sorted implicitly.
This comment doesn't mean much, anymore.
It was added in commit 159428538323 ("arm64: Add Kconfig option for APM
X-Gene SOC family"). Why someone cared so much about the sorting of the
two defaults is unclear to me. Maybe only to make sure future commits
wouldn't mess up the sorting order. Anyhow, it seems it was just
forgotten to remove that line in commit 62aceb8ff4b3 ("arm64: make
default NR_CPUS 8") which again made it a single item list.
> > - default "8"
> > + default "64"
Paul Bolle
next prev parent reply other threads:[~2014-09-09 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 11:44 [PATCH] arm64, defconfig: Increase NR_CPUS default to 64 Robert Richter
2014-09-08 13:00 ` Arnd Bergmann
2014-09-08 13:28 ` Robert Richter
2014-09-08 18:21 ` Mark Rutland
2014-09-09 8:07 ` Uwe Kleine-König
2014-09-09 9:28 ` Paul Bolle [this message]
2014-09-23 10:44 ` Robert Richter
2014-09-23 10:46 ` Mark Rutland
2014-09-23 10:51 ` Robert Richter
2014-09-23 10:47 ` Will Deacon
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=1410254887.22255.14.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).