[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dde7b389-73c6-b218-914c-0b4d76b34a75@caviumnetworks.com>
Date: Fri, 4 Aug 2017 09:41:00 -0700
From: David Daney <ddaney@...iumnetworks.com>
To: James Hogan <james.hogan@...tec.com>,
Yang Shi <yang.shi@...driver.com>
Cc: "david.daney@...ium.com" <david.daney@...ium.com>,
"ralf@...ux-mips.org" <ralf@...ux-mips.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mips@...ux-mips.org" <linux-mips@...ux-mips.org>
Subject: Re: [PATCH] mips: octeon: unselect NR_CPUS_DEFAULT_16
On 08/04/2017 06:27 AM, James Hogan wrote:
> On Sat, Feb 20, 2016 at 12:09:28AM +0000, Yang Shi wrote:
>> In the octeon defconfig, NR_CPUS is 32. And, some model of OCTEON II do have
>>> 16 cores. Given the typical memory size equipped by Octeon boards, it sounds
>> like not a big deal to set a bigger NR_CPUS value as default.
>>
>> Signed-off-by: Yang Shi <yang.shi@...driver.com>
>> ---
>> arch/mips/Kconfig | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
>> index ab433d3..a885156 100644
>> --- a/arch/mips/Kconfig
>> +++ b/arch/mips/Kconfig
>> @@ -885,7 +885,6 @@ config CAVIUM_OCTEON_SOC
>> select USE_OF
>> select ARCH_SPARSEMEM_ENABLE
>> select SYS_SUPPORTS_SMP
>> - select NR_CPUS_DEFAULT_16
>
> So should this select NR_CPUS_DEFAULT_32 instead?
There are OCTEON systems today with 96 CPUs, so something 96 or greater
would let us avoid changing this more than once.
David Daney
>
> Cheers
> James
>
>> select BUILTIN_DTB
>> select MTD_COMPLEX_MAPPINGS
>> help
>> --
>> 2.0.2
>>
>>
Powered by blists - more mailing lists