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]
Message-ID: <47461daf-3aa5-493f-7278-b0116ee2c724@linux.com>
Date: Wed, 17 Jan 2024 11:59:53 -0800 (PST)
From: "Christoph Lameter (Ampere)" <cl@...ux.com>
To: Eric Mackay <eric.mackay@...cle.com>
cc: mark.rutland@....com, Jonathan.Cameron@...wei.com, Matteo.Carlini@....com, 
    Valentin.Schneider@....com, akpm@...ux-foundation.org, 
    anshuman.khandual@....com, catalin.marinas@....com, 
    dave.kleikamp@...cle.com, linux-arm-kernel@...ts.infradead.org, 
    linux-kernel@...r.kernel.org, linux-mm@...ck.org, linux@...linux.org.uk, 
    robin.murphy@....com, vanshikonda@...amperecomputing.com, 
    yang@...amperecomputing.com
Subject: Re: [PATCH] ARM64: Dynamically allocate cpumasks and increase
 supported CPUs to 512

On Tue, 16 Jan 2024, Eric Mackay wrote:

>
> It seems > 256 was chosen as the cutoff simply because it preserves existing behavior.
> The patch description seems to imply there was pushback from distro maintainers on just increasing
> the default NR_CPUS.

Yup that was it.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ