mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Hogan <james.hogan@imgtec.com>
To: Yang Shi <yang.shi@windriver.com>
Cc: "david.daney@cavium.com" <david.daney@cavium.com>,
	"ralf@linux-mips.org" <ralf@linux-mips.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [PATCH] mips: octeon: unselect NR_CPUS_DEFAULT_16
Date: Fri, 4 Aug 2017 14:27:19 +0100	[thread overview]
Message-ID: <20170804132718.GY31455@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <1455926968-12779-1-git-send-email-yang.shi@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 921 bytes --]

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@windriver.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?

Cheers
James

>         select BUILTIN_DTB
>         select MTD_COMPLEX_MAPPINGS
>         help
> --
> 2.0.2
> 
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-08-04 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20  0:09 Yang Shi
2017-08-04 13:27 ` James Hogan [this message]
2017-08-04 16:41   ` David Daney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170804132718.GY31455@jhogan-linux.le.imgtec.org \
    --to=james.hogan@imgtec.com \
    --cc=david.daney@cavium.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=yang.shi@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®