From: rric@kernel.org (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64, defconfig: Increase NR_CPUS default to 64
Date: Mon, 8 Sep 2014 15:28:43 +0200 [thread overview]
Message-ID: <20140908132843.GY4703@rric.localhost> (raw)
In-Reply-To: <3450151.nDuN2aF2Xl@wuerfel>
On 08.09.14 15:00:47, Arnd Bergmann wrote:
> On Monday 08 September 2014 13:44:48 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>
> >
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> FWIW, have you tried what happens when you increase the number further?
> We have architectures on which we support thousands of CPUs, so I wonder
> if there is a point at which this stops working on ARM64.
>
> Are you able to compile and boot a kernel built with e.g. NR_CPUS=256 or
> 4096 on your hardware?
We haven't tried this so far, but it's definitely on our list testing
this.
-Robert
next prev parent reply other threads:[~2014-09-08 13: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 [this message]
2014-09-08 18:21 ` Mark Rutland
2014-09-09 8:07 ` Uwe Kleine-König
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=20140908132843.GY4703@rric.localhost \
--to=rric@kernel.org \
--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).