linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/4] arm64: defconfig: increase NR_CPUS range to 2-128
Date: Fri, 3 Oct 2014 11:58:39 +0100	[thread overview]
Message-ID: <20141003105839.GD26643@leverpostej> (raw)
In-Reply-To: <1411635840-24038-2-git-send-email-ganapatrao.kulkarni@caviumnetworks.com>

On Thu, Sep 25, 2014 at 10:03:56AM +0100, Ganapatrao Kulkarni wrote:
> Raising the maximum limit to 128. This is needed for Cavium's
> Thunder systems that will have 96 cores on Multi-node system.

Has this been tested on any such systems?

Mark.

> 
> Signed-off-by: Ganapatrao Kulkarni <ganapatrao.kulkarni@caviumnetworks.com>
> ---
>  arch/arm64/Kconfig | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 4d42453..a409105 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -296,8 +296,8 @@ config SCHED_SMT
>  	  places. If unsure say N here.
>  
>  config NR_CPUS
> -	int "Maximum number of CPUs (2-64)"
> -	range 2 64
> +	int "Maximum number of CPUs (2-128)"
> +	range 2 128
>  	depends on SMP
>  	# These have to remain sorted largest to smallest
>  	default "64"
> -- 
> 1.8.1.4
> 
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2014-10-03 10:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  9:03 [RFC PATCH 0/4] arm64:numa: Add numa support for arm64 platforms Ganapatrao Kulkarni
2014-09-25  9:03 ` [RFC PATCH 1/4] arm64: defconfig: increase NR_CPUS range to 2-128 Ganapatrao Kulkarni
2014-10-03 10:58   ` Mark Rutland [this message]
2014-10-06  4:29     ` Ganapatrao Kulkarni
2014-09-25  9:03 ` [RFC PATCH 2/4] arm/arm64:dt:numa: adding numa node mapping for memory nodes Ganapatrao Kulkarni
2014-10-03 11:05   ` Mark Rutland
2014-10-06  4:20     ` Ganapatrao Kulkarni
2014-10-06 11:08       ` Mark Rutland
2014-10-06 17:26         ` Ganapatrao Kulkarni
2014-09-25  9:03 ` [RFC PATCH 3/4] arm64:thunder: Add initial dts for Cavium Thunder SoC in 2 Node topology Ganapatrao Kulkarni
2014-10-03 11:19   ` Mark Rutland
2014-09-25  9:03 ` [RFC PATCH 4/4] arm64:numa: adding numa support for arm64 platforms Ganapatrao Kulkarni
2014-10-03 12:13   ` Mark Rutland
2014-10-06  5:14     ` Ganapatrao Kulkarni
2014-10-06 11:26       ` Mark Rutland
2014-10-06 17:52         ` Ganapatrao Kulkarni
2014-10-17 17:19           ` Ganapatrao Kulkarni
2014-10-20 14:25             ` Steve Capper
2014-10-20 14:30               ` Steve Capper
2014-10-22 11:27                 ` Ganapatrao Kulkarni
2014-10-28  8:48             ` Hanjun Guo
2014-10-29  7:20               ` Ganapatrao Kulkarni
2014-09-25  9:04 ` Ganapatrao Kulkarni

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=20141003105839.GD26643@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).