From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64, defconfig: Increase NR_CPUS default to 64
Date: Tue, 9 Sep 2014 10:07:40 +0200 [thread overview]
Message-ID: <20140909080740.GP23009@pengutronix.de> (raw)
In-Reply-To: <1410176689-20020-1-git-send-email-rric@kernel.org>
On Mon, Sep 08, 2014 at 01:44:48PM +0200, Robert Richter wrote:
> From: Robert Richter <rrichter@cavium.com>
>
> Raising the current maximum limit to 64. This is needed for Cavium's
> Thunder systems that will have at least 48 cores per die.
>
> The change keeps the current memory footprint in cpu mask structures.
> It does not break existing code. Setting the maximum to 64 cpus still
> boots systems with less cpus.
>
> Mark's Juno happily booted with a NR_CPUS=64 kernel.
>
> Tested on our Thunder system with 48 cores. We could see interrupts to
> all cores.
>
> Cc: Radha Mohan Chintakuntla <rchintakuntla@cavium.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Robert Richter <rrichter@cavium.com>
> ---
> arch/arm64/Kconfig | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index fd4e81a4e1ce..67fca2ea81a7 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -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.
Best regards
Uwe
> - default "8"
> + default "64"
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-09-09 8:07 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 [this message]
2014-09-09 9:28 ` Paul Bolle
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=20140909080740.GP23009@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).