From nobody Sun May 7 22:24:52 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QDzWR5mZgz49c20 for ; Sun, 7 May 2023 22:25:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QDzWR3C0Xz3l2p for ; Sun, 7 May 2023 22:25:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-50bcb4a81ceso7044053a12.2 for ; Sun, 07 May 2023 15:25:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1683498303; x=1686090303; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9MDL7g+qankNW5HDb7eKTuBPpA290CIqQVPmY97yJe4=; b=sqBygtmSjj+NEcZuSaG411xorAXZDDch8AzlJOXDDjoSTbgIMv8e5ROjiqKste7Fxt pHScaCeFQemJsgQDOMsZ91DAEc27Ny3mPcQtpqHhcukEtTzvL25QqJZRQQkwoX2RuPZ9 yc9xSjJX2b0LyOV4hUuUP6e1a9Rx/j9hO4VdXcgpm+vpAgN9y/pReDuNxcr0i2ISFhvR sfO9kSshpTJiCJLLqs+wsII+OVio7fCihIH/bC/8Vu2yTdGvF4hFW4BvRTtSuOxbo17p PFQXbIhTB3Smt3XOYAODK6jkDv6LsmB5kNnHTMhYx9+074pDwOgyfq7OR7hUlbPhqX8g 49/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683498303; x=1686090303; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9MDL7g+qankNW5HDb7eKTuBPpA290CIqQVPmY97yJe4=; b=lt3CB2OB7j8Wpdt9Q0F1+hwP3IXKYiweQT0bbCn9FlGzFg2NAE9d+OyaFLeGJw0eva ozoLCHdph7rsFpIj7CTVIOgyoLdAZDe56ClSd3GD24WK+r3CvprVfdxPROH0BJ5Z5uYz 89ll01CsrOIUWEfUTXur9mQEDqnDpQpHX02fDyWgdaGtgG3TMt5JB/mTp78Uum/GEOhl MNSmMdJxNLSdUyyVLkJUUcR30B9Zzpfxz37bTt/sqjdEYkPhrE9QkBYApjuVvJ8qXUb8 pCIKD2dWkQJ6l/QqKXfoUGoZRuzo+3/q4rDqKBobjBKoFLmTHzgnYxi1aKw+QGEKcr4V yq+A== X-Gm-Message-State: AC+VfDzKRsIZPvC6cWUJPywzsLmfz0sccmyC4KSIeSbXeQh3/pQnCF2I wV+6e6WAoZP2c1Akst1X1nfGkQ4IsF7dVQBmcV75XQ== X-Google-Smtp-Source: ACHHUZ4W1tXF9nfWdOWnqV5fKqsJAoYS338za8SBVweS4Vhc3/xOczvMfwkOP9k8FMPSWwJHufjUAtC1pSZ8cgZklE8= X-Received: by 2002:a17:907:72d6:b0:960:f1a6:6a12 with SMTP id du22-20020a17090772d600b00960f1a66a12mr7616641ejc.55.1683498303455; Sun, 07 May 2023 15:25:03 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sun, 7 May 2023 16:24:52 -0600 Message-ID: Subject: Re: Support for more than 256 CPU cores To: Moin Rahman Cc: Ed Maste , freebsd-arch , FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000005b94b605fb21fe84" X-Rspamd-Queue-Id: 4QDzWR3C0Xz3l2p X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000005b94b605fb21fe84 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, May 7, 2023, 3:51 PM Moin Rahman wrote: > > > > On May 5, 2023, at 3:38 PM, Ed Maste wrote: > > > > FreeBSD supports up to 256 CPU cores in the default kernel configuratio= n > > (on Tier-1 architectures). Systems with more than 256 cores are > > available now, and will become increasingly common over FreeBSD 14=E2= =80=99s > > lifetime. The FreeBSD Foundation is supporting the effort to increase > > MAXCPU, and PR269572[1] is open to track tasks and changes. > > > > As a project we have scalability work ahead of us to make best use of > > high core count machines, but at a minimum we should be able to boot a > > GENERIC kernel on such systems, and have an ABI for the FreeBSD 14 > > release that supports such a configuration. > > > > Some changes have already been committed in support of increased MAXCPU= , > > including increasing MAX_APIC_ID (commit c8113dad7ed4) and a number of > > changes to reduce bloat (such as commits 42f722e721cd, e72f7ed43eef, > > 78cfa762ebf2 and 74ac712f72cf). > > > > The next step is to increase the maximum cpuset size for userland. > > I have this change open in review D39941[2] and an exp-run request in > > PR271213[3]. Following that the kernel change for increasing MAXCPU is > > in D36838[4]. > > > > Additional work on bloat reduction will continue after this change, and > > looking forward FreeBSD is going to need ongoing effort from the > > community and the FreeBSD Foundation to continue improving scalability. > > > > [1] https://bugs.freebsd.org/269572 > > [2] https://reviews.freebsd.org/D39941 > > [3] https://bugs.freebsd.org/271213 > > [4] https://reviews.freebsd.org/D36838 > > > > By any chance will this be merged into 13? > Nope. It breaks too many kernel KBIs that are exposed to at least some modules. Warner > > Kind regards, > Moin > --0000000000005b94b605fb21fe84 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, May 7, 2023, 3:51 PM Moin Rahman <bofh@freebsd.org> wrote:


> On May 5, 2023, at 3:38 PM, Ed Maste <emaste@freebsd.org> wr= ote:
>
> FreeBSD supports up to 256 CPU cores in the default kernel configurati= on
> (on Tier-1 architectures).=C2=A0 Systems with more than 256 cores are<= br> > available now, and will become increasingly common over FreeBSD 14=E2= =80=99s
> lifetime.=C2=A0 The FreeBSD Foundation is supporting the effort to inc= rease
> MAXCPU, and PR269572[1] is open to track tasks and changes.
>
> As a project we have scalability work ahead of us to make best use of<= br> > high core count machines, but at a minimum we should be able to boot a=
> GENERIC kernel on such systems, and have an ABI for the FreeBSD 14
> release that supports such a configuration.
>
> Some changes have already been committed in support of increased MAXCP= U,
> including increasing MAX_APIC_ID (commit c8113dad7ed4) and a number of=
> changes to reduce bloat (such as commits 42f722e721cd, e72f7ed43eef, > 78cfa762ebf2 and 74ac712f72cf).
>
> The next step is to increase the maximum cpuset size for userland.
> I have this change open in review D39941[2] and an exp-run request in<= br> > PR271213[3].=C2=A0 Following that the kernel change for increasing MAX= CPU is
> in D36838[4].
>
> Additional work on bloat reduction will continue after this change, an= d
> looking forward FreeBSD is going to need ongoing effort from the
> community and the FreeBSD Foundation to continue improving scalability= .
>
> [1] https://bugs.freebsd.org/269572
> [2] https://reviews.freebsd.org/D39941
> [3] https://bugs.freebsd.org/271213
> [4] https://reviews.freebsd.org/D36838
>

By any chance will this be merged into 13?

Nope. It breaks too many kernel K= BIs that are exposed to at least some modules.

<= /div>
Warner

Kind regards,
Moin
--0000000000005b94b605fb21fe84--