lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 11 Jan 2021 09:57:41 -0800
From:   Vanshidhar Konda <vanshikonda@...amperecomputing.com>
To:     Will Deacon <will@...nel.org>
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        catalin.marinas@....com, patches@...erecomputing.com
Subject: Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512

On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
>On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@...amperecomputing.com wrote:
>> From: Vanshidhar Konda <vanshikonda@...amperecomputing.com>
>>
>> Increase the default value of NR_CPUS to 512 from 256. This will
>> enable the defconfig kernel to support platforms that have upto
>> 512 cores.
>
>Do we already support such a platform, and what is it? I'm fine with bumping
>the number, it's just nice to be able to say specifically _why_ we're dong
>it.

I'm not aware of any publicly available systems that run into the 256
core limitation. At Ampere we have internal systems that would benefit
from this change as they support more than 256 cores.

Thanks,
Vanshi

>
>Thanks,
>
>Will

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ