arm64, defconfig: Increase NR_CPUS default to 64
PATCH 1/1 arm64, defconfig: Increase NR_CPUS default to 64
From: Robert Richter <[email protected]>
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.
--- arch/arm64/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/arm64/Kconfig +3 -3
@@ -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"
Signature · 1 line
2.0.1
Quoted 9 lines · On Monday 08 September 2014 13:44:48 Robert Richter wrote:
From: Robert Richter <[email protected]>
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.
Quoted 9 lines
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 <[email protected]>Cc Mark Rutland <[email protected]>Signed-off-by Robert Richter <[email protected]>
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
Quoted 20 lines · Arnd Bergmann
Quoted 9 lines · On Monday 08 September 2014 13:44:48 Robert Richter wrote:
From: Robert Richter <[email protected]>
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.
Quoted 9 lines
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 <[email protected]>Cc Mark Rutland <[email protected]>Signed-off-by Robert Richter <[email protected]>
Quoted 8 lines
Acked-by Arnd Bergmann <[email protected]>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
Quoted 11 lines · Arnd Bergmann
Quoted 10 lines · On Monday 08 September 2014 13:44:48 Robert Richter wrote:
From: Robert Richter <[email protected]>
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.
FWIW, I've just (boot-)tested this precise patch on my Juno atop of v3.17-rc3, so:
Quoted 9 lines
Quoted 8 lines
Tested on our Thunder system with 48 cores. We could see interrupts to all cores.
Cc Radha Mohan Chintakuntla <[email protected]>Cc Mark Rutland <[email protected]>Signed-off-by Robert Richter <[email protected]>
Quoted 8 lines
Acked-by Arnd Bergmann <[email protected]>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?
Compiling seems to work fine at least up to 4096 CPUs, and an NR_CPUS=4096 kernel boots happily on Juno, logs below for 8, 64, 256, and 4096 CPUs.
Somehow the Image for NR_CPUs=8 is larger than that for 64. That struck me as suspicious, but I'm able to duplicate those builds quite easily. We seem to lose 4k of kernel code and 10k of rwdata going from 8 to 64 CPUs. It does mean that bumping NR_CPUS to 64 is a nice size reducation for the moment, though ;)
I'm using the Linaro 14.05 GCC 4.9 (little-endian) toolchain, in case anyone wants to try and reproduce that.
Obviously this would be much more interesting with more physical CPUs; KVM is currently limited to 8 so I can't even fake it for the moment.
Thanks,
Mark.
---->8----
[mark at leverpostej:~/src/linux]% ls -al Image-8 -rwxrwxr-x 1 mark mark 6800880 Sep 8 18:47 Image-8
Memory: 8188636K/8371264K available (4508K kernel code, 317K rwdata, 1588K rodata, 216K init, 218K bss, 182628K reserved) Virtual kernel memory layout:
vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000 ( 247 GB)
vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000 ( 7 GB maximum)
0xffffffbe01c00000 - 0xffffffbe23000000 ( 532 MB actual)
PCI I/O : 0xffffffbffa000000 - 0xffffffbffb000000 ( 16 MB)
fixed : 0xffffffbffbdfe000 - 0xffffffbffbdff000 ( 4 KB)
modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
memory : 0xffffffc000000000 - 0xffffffc980000000 ( 38912 MB)
.init : 0xffffffc000676000 - 0xffffffc0006ac3c0 ( 217 KB)
.text : 0xffffffc000080000 - 0xffffffc0006751e4 ( 6101 KB)
.data : 0xffffffc0006ad000 - 0xffffffc0006fc5f0 ( 318 KB)SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1 Preemptible hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=6.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6 NR_IRQS:64 nr_irqs:64 0
----
[mark at leverpostej:~/src/linux]% ls -al Image-64 -rwxrwxr-x 1 mark mark 6786800 Sep 8 18:48 Image-64
Memory: 8188664K/8371264K available (4504K kernel code, 307K rwdata, 1588K rodata, 216K init, 223K bss, 182600K reserved) Virtual kernel memory layout:
vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000 ( 247 GB)
vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000 ( 7 GB maximum)
0xffffffbe01c00000 - 0xffffffbe23000000 ( 532 MB actual)
PCI I/O : 0xffffffbffa000000 - 0xffffffbffb000000 ( 16 MB)
fixed : 0xffffffbffbdfe000 - 0xffffffbffbdff000 ( 4 KB)
modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
memory : 0xffffffc000000000 - 0xffffffc980000000 ( 38912 MB)
.init : 0xffffffc000675000 - 0xffffffc0006ab3c0 ( 217 KB)
.text : 0xffffffc000080000 - 0xffffffc0006741e4 ( 6097 KB)
.data : 0xffffffc0006ac000 - 0xffffffc0006f8ef0 ( 308 KB)SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1 Preemptible hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=6.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6 NR_IRQS:64 nr_irqs:64 0
----
mark at leverpostej:~/src/linux]% ls -al Image-256 -rwxrwxr-x 1 mark mark 6810096 Sep 8 19:04 Image-256
Memory: 8188572K/8371264K available (4508K kernel code, 322K rwdata, 1588K rodata, 221K init, 262K bss, 182692K reserved) Virtual kernel memory layout:
vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000 ( 247 GB)
vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000 ( 7 GB maximum)
0xffffffbe01c00000 - 0xffffffbe23000000 ( 532 MB actual)
PCI I/O : 0xffffffbffa000000 - 0xffffffbffb000000 ( 16 MB)
fixed : 0xffffffbffbdfe000 - 0xffffffbffbdff000 ( 4 KB)
modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
memory : 0xffffffc000000000 - 0xffffffc980000000 ( 38912 MB)
.init : 0xffffffc000676000 - 0xffffffc0006ad400 ( 221 KB)
.text : 0xffffffc000080000 - 0xffffffc0006751e4 ( 6101 KB)
.data : 0xffffffc0006ae000 - 0xffffffc0006fe9f0 ( 323 KB)SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1 Preemptible hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=6.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6 NR_IRQS:64 nr_irqs:64 0
----
[mark at leverpostej:~/src/linux]% ls -al Image-4096 -rwxrwxr-x 1 mark mark 7050480 Sep 8 18:51 Image-4096
Memory: 8183572K/8371264K available (4508K kernel code, 497K rwdata, 1620K rodata, 250K init, 4797K bss, 187692K reserved) Virtual kernel memory layout:
vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000 ( 247 GB)
vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000 ( 7 GB maximum)
0xffffffbe01c00000 - 0xffffffbe23000000 ( 532 MB actual)
PCI I/O : 0xffffffbffa000000 - 0xffffffbffb000000 ( 16 MB)
fixed : 0xffffffbffbdfe000 - 0xffffffbffbdff000 ( 4 KB)
modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
memory : 0xffffffc000000000 - 0xffffffc980000000 ( 38912 MB)
.init : 0xffffffc00067e000 - 0xffffffc0006bcb80 ( 251 KB)
.text : 0xffffffc000080000 - 0xffffffc00067d1e4 ( 6133 KB)
.data : 0xffffffc0006bd000 - 0xffffffc0007394f0 ( 498 KB)SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1 Preemptible hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=4096 to nr_cpu_ids=6.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6 NR_IRQS:64 nr_irqs:64 0
Quoted 26 lines · Robert Richter
From: Robert Richter <[email protected]>
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 <[email protected]>Cc Mark Rutland <[email protected]>Signed-off-by Robert Richter <[email protected]>--- arch/arm64/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)arch/arm64/Kconfig +0
-0
arch/arm64/Kconfig config SCHED_SMT · line 258
Quoted 9 lines
arch/arm64/Kconfig +2
-2@@ -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
Quoted 2 lines
arch/arm64/Kconfig +1
-1- default "8" + default "64"
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |
Quoted 4 lines · Uwe Kleine-K?nig
Quoted 3 lines · Robert Richter
arch/arm64/Kconfig +0
-0@@ -252,11 +252,11 @@ config SCHED_SMT places. If unsure say N here.
Quoted 9 lines
arch/arm64/Kconfig config SCHED_SMT · line 258
Quoted 7 lines
arch/arm64/Kconfig +2
-2config 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 smallestUnrelated 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.
Quoted 2 lines
arch/arm64/Kconfig config SCHED_SMT · line 259
Quoted 2 lines
arch/arm64/Kconfig +1
-1- default "8" + default "64"
Paul Bolle
Quoted 5 lines · Robert Richter
From: Robert Richter <[email protected]>
Raising the current maximum limit to 64. This is needed for Cavium's Thunder systems that will have at least 48 cores per die.
Quoted 8 lines
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
Quoted 30 lines
Cc Radha Mohan Chintakuntla <[email protected]>Cc Mark Rutland <[email protected]>Signed-off-by Robert Richter <[email protected]>--- arch/arm64/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)arch/arm64/Kconfig +3
-3@@ -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"Signature · 1 line
2.0.1
Mark Rutland
reviewerHi Robert,
Quoted 10 lines · Robert Richter
Quoted 9 lines · Robert Richter
From: Robert Richter <[email protected]>
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.
Quoted 8 lines
Quoted 4 lines
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.
This is already in the arm64 for-next/core branch [1].
Mark.
Quoted 36 lines
Thanks,
-Robert
Quoted 30 lines
Cc Radha Mohan Chintakuntla <[email protected]>Cc Mark Rutland <[email protected]>Signed-off-by Robert Richter <[email protected]>--- arch/arm64/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)arch/arm64/Kconfig +3
-3@@ -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"Signature · 1 line
2.0.1
Quoted 10 lines · Robert Richter
Quoted 9 lines · Robert Richter
From: Robert Richter <[email protected]>
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.
Quoted 8 lines
Quoted 4 lines
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.
I thought this was queued already?
Will
Quoted 11 lines · Mark Rutland
Quoted 4 lines · Robert Richter
On 08.09.14 13:44:48, Robert Richter wrote:
Catalin, Will,please consider applying this patch.
This is already in the arm64 for-next/core branch [1].
Mark.
Ah, thanks for the pointer.
-Robert