All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	Ariel Elior <aelior@marvell.com>,
	GR-everest-linux-l2@marvell.com, Wei Liu <wei.liu@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>,
	Netdev <netdev@vger.kernel.org>,
	lkft-triage@lists.linaro.org, Arnd Bergmann <arnd@arndb.de>,
	"David S. Miller" <davem@davemloft.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: ipv4/tcp.c:4234:1: error: the frame size of 1152 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
Date: Tue, 7 Sep 2021 18:43:46 -0700	[thread overview]
Message-ID: <CAHk-=wi+O66NwiiAYBeS6kiix6YGuDvPf-MPddtycE_D4fWV=g@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whcFKGyJOgmwJtWwDCP7VFPydnTtsvjPL6ZP6d6gTyPDQ@mail.gmail.com>

On Tue, Sep 7, 2021 at 6:35 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> I think a lot of them have just copied the x86 code (it was 4k long
> ago), without actually understanding all the details.

Just to put the x86 number in perspective: it was raised to 8192 back
in 2013, with the comment

    x86/cpu: Increase max CPU count to 8192

    The MAXSMP option is intended to enable silly large numbers of
    CPUs for testing purposes.  The current value of 4096 isn't very
    silly any longer as there are actual SGI machines that approach
    6096 CPUs when taking HT into account.

    Increase the value to a nice round 8192 to account for this and
    allow for short term future increases.

so on the x86 side, people have actually done these things.

Other architectures? I think some IBM power9 machines can hit 192
cores (with SMT4 - so NR_CPUS of 768), but I don't think there's been
an equivalent of an SGI for anything but x86.

But admittedly I haven't checked or followed those things. I could
easily imagine some boutique super-beefy setup.

               Linus

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Mathias Nyman <mathias.nyman@intel.com>,
	 Johannes Berg <johannes@sipsolutions.net>,
	Jakub Kicinski <kuba@kernel.org>,
	 Shuah Khan <skhan@linuxfoundation.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	 Ariel Elior <aelior@marvell.com>,
	GR-everest-linux-l2@marvell.com,  Wei Liu <wei.liu@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>,
	Netdev <netdev@vger.kernel.org>,
	 lkft-triage@lists.linaro.org, Arnd Bergmann <arnd@arndb.de>,
	 "David S. Miller" <davem@davemloft.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 Nick Desaulniers <ndesaulniers@google.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	 Alexei Starovoitov <ast@kernel.org>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: ipv4/tcp.c:4234:1: error: the frame size of 1152 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
Date: Tue, 7 Sep 2021 18:43:46 -0700	[thread overview]
Message-ID: <CAHk-=wi+O66NwiiAYBeS6kiix6YGuDvPf-MPddtycE_D4fWV=g@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whcFKGyJOgmwJtWwDCP7VFPydnTtsvjPL6ZP6d6gTyPDQ@mail.gmail.com>

On Tue, Sep 7, 2021 at 6:35 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> I think a lot of them have just copied the x86 code (it was 4k long
> ago), without actually understanding all the details.

Just to put the x86 number in perspective: it was raised to 8192 back
in 2013, with the comment

    x86/cpu: Increase max CPU count to 8192

    The MAXSMP option is intended to enable silly large numbers of
    CPUs for testing purposes.  The current value of 4096 isn't very
    silly any longer as there are actual SGI machines that approach
    6096 CPUs when taking HT into account.

    Increase the value to a nice round 8192 to account for this and
    allow for short term future increases.

so on the x86 side, people have actually done these things.

Other architectures? I think some IBM power9 machines can hit 192
cores (with SMT4 - so NR_CPUS of 768), but I don't think there's been
an equivalent of an SGI for anything but x86.

But admittedly I haven't checked or followed those things. I could
easily imagine some boutique super-beefy setup.

               Linus

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-09-08  1:44 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 12:27 ipv4/tcp.c:4234:1: error: the frame size of 1152 bytes is larger than 1024 bytes [-Werror=frame-larger-than=] Naresh Kamboju
2021-09-06 12:27 ` Naresh Kamboju
2021-09-07 22:16 ` Linus Torvalds
2021-09-07 22:16   ` Linus Torvalds
2021-09-07 23:14   ` Linus Torvalds
2021-09-07 23:14     ` Linus Torvalds
2021-09-07 23:35     ` Nathan Chancellor
2021-09-07 23:35       ` Nathan Chancellor
2021-09-07 23:49       ` Linus Torvalds
2021-09-07 23:49         ` Linus Torvalds
2021-09-08  0:15         ` Nathan Chancellor
2021-09-08  0:15           ` Nathan Chancellor
2021-09-08  1:35           ` Linus Torvalds
2021-09-08  1:35             ` Linus Torvalds
2021-09-08  1:43             ` Linus Torvalds [this message]
2021-09-08  1:43               ` Linus Torvalds
2021-09-08 17:00               ` Arnd Bergmann
2021-09-08 17:00                 ` Arnd Bergmann
2021-09-08  7:09     ` Johannes Berg
2021-09-08  7:09       ` Johannes Berg
2021-09-08 10:03     ` Wei Liu
2021-09-08 10:03       ` Wei Liu
2021-09-08 14:51       ` David Laight
2021-09-08 14:51         ` David Laight
2021-09-08 15:23         ` Wei Liu
2021-09-08 15:23           ` Wei Liu
2021-09-08 16:05           ` David Laight
2021-09-08 16:05             ` David Laight
2021-09-08 15:59       ` Linus Torvalds
2021-09-08 15:59         ` Linus Torvalds
2021-09-08 16:12         ` Wei Liu
2021-09-08 16:12           ` Wei Liu
2021-09-08 13:48     ` Thorsten Glaser
2021-09-08 13:48       ` Thorsten Glaser
2021-09-08 14:50       ` Eric Dumazet
2021-09-08 14:50         ` Eric Dumazet
2021-09-08 15:48         ` Linus Torvalds
2021-09-08 15:48           ` Linus Torvalds
2021-09-08 16:56           ` Arnd Bergmann
2021-09-08 16:56             ` Arnd Bergmann
2021-09-08 14:11     ` Shuah Khan
2021-09-08 14:11       ` Shuah Khan
2021-09-08 17:05       ` Arnd Bergmann
2021-09-08 17:05         ` Arnd Bergmann
2021-09-08 17:16         ` Shuah Khan
2021-09-08 17:16           ` Shuah Khan
2021-09-08 21:24           ` Brendan Higgins
2021-09-08 21:24             ` Brendan Higgins
2021-09-08 22:27             ` Linus Torvalds
2021-09-08 22:27               ` Linus Torvalds
2021-09-13 20:55             ` Shuah Khan
2021-09-13 20:55               ` Shuah Khan
2021-09-14 20:46               ` Brendan Higgins
2021-09-14 20:46                 ` Brendan Higgins
2021-09-14 22:03                 ` Arnd Bergmann
2021-09-14 22:03                   ` Arnd Bergmann
2021-09-17  5:39                   ` Brendan Higgins
2021-09-17  5:39                     ` Brendan Higgins
2021-09-17  6:16                     ` Brendan Higgins
2021-09-17  6:16                       ` Brendan Higgins
2021-09-17  7:20                       ` Arnd Bergmann
2021-09-17  7:20                         ` Arnd Bergmann

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='CAHk-=wi+O66NwiiAYBeS6kiix6YGuDvPf-MPddtycE_D4fWV=g@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=GR-everest-linux-l2@marvell.com \
    --cc=aelior@marvell.com \
    --cc=arnd@arndb.de \
    --cc=ast@kernel.org \
    --cc=brendanhiggins@google.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mathias.nyman@intel.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=wei.liu@kernel.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.