From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "Thomas Gleixner" <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
"Peter Zijlstra" <peterz@infradead.org>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>
Subject: Re: [RFC PATCH] futex: Dynamically allocate futex_queues depending on nr_node_ids
Date: Wed, 25 Feb 2026 09:06:08 +0530 [thread overview]
Message-ID: <d352dc77-c24d-44eb-bcfa-16fa603ea15a@amd.com> (raw)
In-Reply-To: <20260224111342.-9hafXl5@linutronix.de>
Hello Sebastian,
On 2/24/2026 4:43 PM, Sebastian Andrzej Siewior wrote:
> My question was initially is 1024 for max-nodes something that people
> really use. It was introduced as of
> https://lore.kernel.org/all/alpine.DEB.2.00.1003101537330.30724@chino.kir.corp.google.com/
>
> but it looks odd. It might just one or two machines which are left :)
I have it on good faith that some EPYC user on distro kernels turn on
"L3 as NUMA" option which currently results into 32 NUMA nodes on our
largest configuration.
Adding a little bit more margin for CXL nodes should make even
CONFIG_NODES_SHIFT=6 pretty sane default for most real-word configs.
I don't think we can go more than 10 or so CXL nodes considering the
number of PCIe lanes unless there are more creative ways to attach
tiered memory that appear as a NUMA node.
I'm not sure if Intel has similar crazy combination but NODES_SHIFT=6
can accommodate (16 socket * SNC-3) + up to 16 CXL nodes so it should
be fine for most distro users too?
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-02-25 3:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 10:13 K Prateek Nayak
2026-02-24 11:13 ` Sebastian Andrzej Siewior
2026-02-25 3:36 ` K Prateek Nayak [this message]
2026-02-25 7:39 ` Sebastian Andrzej Siewior
2026-02-25 8:51 ` K Prateek Nayak
2026-02-25 9:22 ` Sebastian Andrzej Siewior
2026-02-27 8:47 ` K Prateek Nayak
2026-02-27 15:15 ` Sebastian Andrzej Siewior
2026-02-27 16:04 ` K Prateek Nayak
2026-02-27 14:42 ` Peter Zijlstra
2026-02-27 14:59 ` K Prateek Nayak
2026-02-27 16:18 ` Peter Zijlstra
2026-02-27 17:12 ` Sebastian Andrzej Siewior
2026-02-27 17:18 ` Peter Zijlstra
2026-03-02 4:59 ` K Prateek Nayak
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=d352dc77-c24d-44eb-bcfa-16fa603ea15a@amd.com \
--to=kprateek.nayak@amd.com \
--cc=andrealmeid@igalia.com \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome