From: Will Deacon <will@kernel.org>
To: vanshikonda@os.amperecomputing.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
patches@amperecomputing.com
Subject: Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
Date: Mon, 11 Jan 2021 10:56:36 +0000 [thread overview]
Message-ID: <20210111105636.GA7071@willie-the-truck> (raw)
In-Reply-To: <20210110053615.3594358-1-vanshikonda@os.amperecomputing.com>
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.
Thanks,
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: vanshikonda@os.amperecomputing.com
Cc: catalin.marinas@arm.com, patches@amperecomputing.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
Date: Mon, 11 Jan 2021 10:56:36 +0000 [thread overview]
Message-ID: <20210111105636.GA7071@willie-the-truck> (raw)
In-Reply-To: <20210110053615.3594358-1-vanshikonda@os.amperecomputing.com>
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.
Thanks,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-11 10:57 UTC|newest]
Thread overview: 16+ 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-10 5:36 ` vanshikonda
2021-01-11 10:56 ` Will Deacon [this message]
2021-01-11 10:56 ` Will Deacon
2021-01-11 17:57 ` Vanshidhar Konda
2021-01-11 17:57 ` Vanshidhar Konda
2021-01-11 18:03 ` Randy Dunlap
2021-01-11 18:03 ` Randy Dunlap
2021-01-11 18:24 ` Vanshi Konda
2021-01-11 18:24 ` Vanshi Konda
2021-01-11 18:25 ` Catalin Marinas
2021-01-11 18:25 ` Catalin Marinas
2021-01-12 5:20 ` Vanshidhar Konda
2021-01-12 5:20 ` Vanshidhar Konda
2021-01-12 14:27 ` Will Deacon
2021-01-12 14:27 ` 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=20210111105636.GA7071@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=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 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.