All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64, defconfig: Increase NR_CPUS default to 64
Date: Tue, 23 Sep 2014 11:47:16 +0100	[thread overview]
Message-ID: <20140923104716.GG26472@arm.com> (raw)
In-Reply-To: <20140923104431.GF20170@rric.localhost>

On Tue, Sep 23, 2014 at 11:44:31AM +0100, Robert Richter wrote:
> On 08.09.14 13:44:48, Robert Richter wrote:
> > From: Robert Richter <rrichter@cavium.com>
> > 
> > Raising the current maximum limit to 64. This is needed for Cavium's
> > Thunder systems that will have at least 48 cores per die.
> > 
> > The change keeps the current memory footprint in cpu mask structures.
> > It does not break existing code. Setting the maximum to 64 cpus still
> > boots systems with less cpus.
> > 
> > Mark's Juno happily booted with a NR_CPUS=64 kernel.
> > 
> > Tested on our Thunder system with 48 cores. We could see interrupts to
> > all cores.
> 
> Catalin, Will,
> 
> please consider applying this patch.

I thought this was queued already?

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Robert Richter <rric@kernel.org>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
	Robert Richter <rrichter@cavium.com>,
	Radha Mohan Chintakuntla <rchintakuntla@cavium.com>,
	Mark Rutland <Mark.Rutland@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64, defconfig: Increase NR_CPUS default to 64
Date: Tue, 23 Sep 2014 11:47:16 +0100	[thread overview]
Message-ID: <20140923104716.GG26472@arm.com> (raw)
In-Reply-To: <20140923104431.GF20170@rric.localhost>

On Tue, Sep 23, 2014 at 11:44:31AM +0100, Robert Richter wrote:
> On 08.09.14 13:44:48, Robert Richter wrote:
> > From: Robert Richter <rrichter@cavium.com>
> > 
> > Raising the current maximum limit to 64. This is needed for Cavium's
> > Thunder systems that will have at least 48 cores per die.
> > 
> > The change keeps the current memory footprint in cpu mask structures.
> > It does not break existing code. Setting the maximum to 64 cpus still
> > boots systems with less cpus.
> > 
> > Mark's Juno happily booted with a NR_CPUS=64 kernel.
> > 
> > Tested on our Thunder system with 48 cores. We could see interrupts to
> > all cores.
> 
> Catalin, Will,
> 
> please consider applying this patch.

I thought this was queued already?

Will

  parent reply	other threads:[~2014-09-23 10:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 11:44 [PATCH] arm64, defconfig: Increase NR_CPUS default to 64 Robert Richter
2014-09-08 11:44 ` Robert Richter
2014-09-08 13:00 ` Arnd Bergmann
2014-09-08 13:00   ` Arnd Bergmann
2014-09-08 13:28   ` Robert Richter
2014-09-08 13:28     ` Robert Richter
2014-09-08 18:21   ` Mark Rutland
2014-09-08 18:21     ` Mark Rutland
2014-09-09  8:07 ` Uwe Kleine-König
2014-09-09  8:07   ` Uwe Kleine-König
2014-09-09  9:28   ` Paul Bolle
2014-09-09  9:28     ` Paul Bolle
2014-09-23 10:44 ` Robert Richter
2014-09-23 10:44   ` Robert Richter
2014-09-23 10:46   ` Mark Rutland
2014-09-23 10:46     ` Mark Rutland
2014-09-23 10:51     ` Robert Richter
2014-09-23 10:51       ` Robert Richter
2014-09-23 10:47   ` Will Deacon [this message]
2014-09-23 10:47     ` Will Deacon

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=20140923104716.GG26472@arm.com \
    --to=will.deacon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.