[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140923104431.GF20170@rric.localhost>
Date: Tue, 23 Sep 2014 12:44:31 +0200
From: Robert Richter <rric@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>
Cc: Robert Richter <rrichter@...ium.com>,
Radha Mohan Chintakuntla <rchintakuntla@...ium.com>,
Mark Rutland <mark.rutland@....com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64, defconfig: Increase NR_CPUS default to 64
On 08.09.14 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.
Catalin, Will,
please consider applying this patch.
Thanks,
-Robert
>
> Cc: Radha Mohan Chintakuntla <rchintakuntla@...ium.com>
> Cc: Mark Rutland <mark.rutland@....com>
> Signed-off-by: Robert Richter <rrichter@...ium.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
> - default "8"
> + default "64"
>
> config HOTPLUG_CPU
> bool "Support for hot-pluggable CPUs"
> --
> 2.0.1
>
--
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