[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3450151.nDuN2aF2Xl@wuerfel>
Date: Mon, 08 Sep 2014 15:00:47 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Robert Richter <rric@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Robert Richter <rrichter@...ium.com>,
Mark Rutland <mark.rutland@....com>,
Radha Mohan Chintakuntla <rchintakuntla@...ium.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64, defconfig: Increase NR_CPUS default to 64
On Monday 08 September 2014 13:44:48 Robert Richter wrote:
> From: Robert Richter <rrichter@...ium.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@...ium.com>
> Cc: Mark Rutland <mark.rutland@....com>
> Signed-off-by: Robert Richter <rrichter@...ium.com>
>
Acked-by: Arnd Bergmann <arnd@...db.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?
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists