From: Jan Glauber <jglauber@cavium.com>
To: arnd@arndb.de, catalin.marinas@arm.com, will.deacon@arm.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jan Glauber <jglauber@cavium.com>
Subject: [PATCH 2/2] arm64: defconfig: Raise NR_CPUS to 256
Date: Fri, 2 Mar 2018 15:37:37 +0100 [thread overview]
Message-ID: <20180302143737.10788-2-jglauber@cavium.com> (raw)
In-Reply-To: <20180302143737.10788-1-jglauber@cavium.com>
ThunderX1 dual socket has 96 CPUs and ThunderX2 has 224 CPUs.
Therefore raise the default number of CPUs from 64 to 256
by adding an arm64 specific option to override the generic default.
Signed-off-by: Jan Glauber <jglauber@cavium.com>
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 3594aefa496f..970950e8c76b 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -630,3 +630,4 @@ CONFIG_CRYPTO_AES_ARM64_CE_BLK=y
CONFIG_CRYPTO_AES_ARM64_NEON_BLK=m
CONFIG_CRYPTO_CHACHA20_NEON=m
CONFIG_CRYPTO_AES_ARM64_BS=m
+CONFIG_NR_CPUS=256
--
2.7.4
next prev parent reply other threads:[~2018-03-02 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 14:37 [PATCH 1/2] arm64: defconfig: enable THUNDER_NIC_VF Jan Glauber
2018-03-02 14:37 ` Jan Glauber [this message]
2018-03-06 13:12 ` [PATCH 2/2] arm64: defconfig: Raise NR_CPUS to 256 Arnd Bergmann
2018-03-06 14:02 ` Jan Glauber
2018-03-06 14:30 ` Arnd Bergmann
2018-03-26 8:52 ` Jan Glauber
2018-03-26 9:28 ` Arnd Bergmann
2018-03-26 10:02 ` Jan Glauber
2018-04-30 9:36 ` [PATCH 1/2] arm64: defconfig: enable THUNDER_NIC_VF Jan Glauber
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=20180302143737.10788-2-jglauber@cavium.com \
--to=jglauber@cavium.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will.deacon@arm.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®