LKML Archive on
help / color / mirror / Atom feed
From: Arnd Bergmann <>
To: Jan Glauber <>
Cc: Catalin Marinas <>,
	Will Deacon <>,
	Linux ARM <>,
	Linux Kernel Mailing List <>
Subject: Re: [PATCH 2/2] arm64: defconfig: Raise NR_CPUS to 256
Date: Tue, 6 Mar 2018 14:12:29 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Mar 2, 2018 at 3:37 PM, Jan Glauber <> wrote:
> ThunderX1 dual socket has 96 CPUs and ThunderX2 has 224 CPUs.

Are you sure about those numbers? From my counting, I would have expected
twice that number in both cases: 48 cores, 2 chips and 2x SMT for ThunderX
vs 52 Cores, 2 chips and 4x SMT for ThunderX2.

> Therefore raise the default number of CPUs from 64 to 256
> by adding an arm64 specific option to override the generic default.

Regardless of what the correct numbers for your chips are, I'd like
to hear some other opinions on how high we should raise that default
limit, both in arch/arm64/Kconfig and in the defconfig file.

As I remember it, there is a noticeable cost for taking the limit beyond
BITS_PER_LONG, both in terms of memory consumption and also
runtime performance (copying and comparing CPU masks).

I'm sure someone will keep coming up with even larger configurations
in the future, so we should try to decide how far we can take the
defaults for the moment without impacting users of the smallest
systems. Alternatively, you could add some measurements that
show how much memory and CPU time is used up on a typical
configuration for a small system (4 cores, no SMT, 512 MB RAM).
If that's low enough, we could just do it anyway.


  reply	other threads:[~2018-03-06 13:12 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 ` [PATCH 2/2] arm64: defconfig: Raise NR_CPUS to 256 Jan Glauber
2018-03-06 13:12   ` Arnd Bergmann [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \
    --subject='Re: [PATCH 2/2] arm64: defconfig: Raise NR_CPUS to 256' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).