From: Will Deacon <will@kernel.org>
To: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, patches@amperecomputing.com
Subject: Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
Date: Tue, 12 Jan 2021 14:27:05 +0000 [thread overview]
Message-ID: <20210112142705.GB9524@willie-the-truck> (raw)
In-Reply-To: <20210112052003.eeg725mmnyv67eop@con01sys-r111.scc-lab.amperecomputing.com>
On Mon, Jan 11, 2021 at 09:20:03PM -0800, Vanshidhar Konda wrote:
> On Mon, Jan 11, 2021 at 06:25:27PM +0000, Catalin Marinas wrote:
> > On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
> > > On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
> > > > On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
> > > >> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
> > > >>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
> > > >>>
> > > >>> Increase the default value of NR_CPUS to 512 from 256. This will
> > > >>> enable the defconfig kernel to support platforms that have upto
> > > >>> 512 cores.
> > > >>
> > > >> Do we already support such a platform, and what is it? I'm fine with bumping.
> > > >> the number, it's just nice to be able to say specifically _why_ we're dong
> > > >> it.
> > > >
> > > > I'm not aware of any publicly available systems that run into the 256
> > > > core limitation. At Ampere we have internal systems that would benefit
> > > > from this change as they support more than 256 cores.
> > >
> > > But what does that have to do with the default value?
> > > Do you expect to run defconfig kernels?
> > > I don't ever expect that.
> >
> > We still aim for the arm64 defconfig to run on all supported SoCs, even
> > if not optimally. Distros indeed tweak the config to their needs.
>
> Would "all supported SoCs" mean only SoCs that are currently available
> publicly? Could we include support for SoCs/systems in development but
> to be available publicly in the next few years?
I don't really see the need to rush that into defconfig, so I'd prefer
to make the update when something actually exists otherwise it's really
hard to keep track of why we made the decision (especially as unreleased
hardware is liable to change).
Will
prev parent reply other threads:[~2021-01-12 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 5:36 [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512 vanshikonda
2021-01-11 10:56 ` Will Deacon
2021-01-11 17:57 ` Vanshidhar Konda
2021-01-11 18:03 ` Randy Dunlap
2021-01-11 18:24 ` Vanshi Konda
2021-01-11 18:25 ` Catalin Marinas
2021-01-12 5:20 ` Vanshidhar Konda
2021-01-12 14:27 ` Will Deacon [this message]
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=20210112142705.GB9524@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=rdunlap@infradead.org \
--cc=vanshikonda@os.amperecomputing.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;
as well as URLs for NNTP newsgroup(s).