Bug#983923: linux-image-4.19.0-13-cloud-amd64: Please add CONFIG_MAXSMP to the linux-image-cloud-amd64 kernel
On Wed, Mar 03, 2021 at 05:35:42PM +0100, Louis Bouchard wrote:
> Thank you for the quick update. I just want to mention that this makes the
> Debian Buster cloud image unusable for any VM with more than 64 cpus.
Is it the number of physical cores that matters, rather than the SMT
threads? Because on a 96 core SMT system, it works today:
admin@ip-10-0-0-75:~$ uname -a && ec2metadata --instance-type && lscpu
Linux ip-10-0-0-75 4.19.0-14-cloud-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
m5a.24xlarge
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
CPU(s): 96
On-line CPU(s) list: 0-95
Thread(s) per core: 2
Core(s) per socket: 24
Socket(s): 2
NUMA node(s): 6
Vendor ID: AuthenticAMD
CPU family: 23
Model: 1
Model name: AMD EPYC 7571
Stepping: 2
CPU MHz: 2550.330
BogoMIPS: 4399.61
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 64K
L2 cache: 512K
L3 cache: 8192K
NUMA node0 CPU(s): 0-7,48-55
NUMA node1 CPU(s): 8-15,56-63
NUMA node2 CPU(s): 16-23,64-71
NUMA node3 CPU(s): 24-31,72-79
NUMA node4 CPU(s): 32-39,80-87
NUMA node5 CPU(s): 40-47,88-95
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid amd_dcm aperfmperf tsc_known_freq pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch topoext perfctr_core vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 clzero xsaveerptr arat npt nrip_save
Do any of the cloud providers supported by the cloud kernel build
(primarily AWS and Azure) offer VMs with >64 physical cores?
noah
Reply to: