[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZaZnYrv/QThRjW2Q@shell.armlinux.org.uk>
Date: Tue, 16 Jan 2024 11:24:18 +0000
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Eric Mackay <eric.mackay@...cle.com>
Cc: cl@...ux.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,
robin.murphy@....com, vanshikonda@...amperecomputing.com,
yang@...amperecomputing.com
Subject: Re: [PATCH] ARM64: Dynamically allocate cpumasks and increase
supported CPUs to 512
On Mon, Jan 15, 2024 at 03:59:11PM -0800, Eric Mackay wrote:
> Whitespace issues aside, I have applied the patch on top of kernel 6.1.55 and tested on both a dual-socket Ampere Altra machine with < 256 CPUs, and a dual-socket AmpereOne machine with > 256 CPUs. Works as expected, with all CPUs visible and functional.
>
> > config NR_CPUS
> > int "Maximum number of CPUs (2-4096)"
> > range 2 4096
> > - default "256"
> > + default 512
>
> Nit: the new default value should be in quotation marks, if we want to be pedantic
I can't find anything that requires the quotes - and as "range" doesn't
for consistency it seems that default shouldn't either. There's nothing
in the documentation that indicates quotes should be used, and looking
at the code, it's just treated as a string. The only thing that quotes
seem to do is to ensure that whitespace will be included.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists