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: Fri, 27 Feb 2026 21:34:40 +0530 [thread overview]
Message-ID: <6be36f62-91bb-4876-8ac5-4ebc4a4a7746@amd.com> (raw)
In-Reply-To: <20260227151518.NzmS3z7E@linutronix.de>
Hello Sebastian,
On 2/27/2026 8:45 PM, Sebastian Andrzej Siewior wrote:
>>> Sounds like it. What would be sane default upper limit then? Something
>>> like 1024 CPUs? 2048? Or even more than that?
>>
>> I feel the current default for NR_CPUS can be be retained as is just to
>> be on the safer side.
>>
>> Turns out QEMU allows for a ridiculous amount of vCPUs per guest and I've
>> found enough evidence of extremely large guests running oversubscribed
>> that sometimes run distro kernels :-(
>
> You mean distro kernel in 8k CPUs guest? I do this kind of things for
> testing but not with a distro kernel. Oh well.
I bet there are interesting justifications with stuff like live
migration, reliability, etc. but I haven't dared to ask!
>
>> I'll let you decide what is a good trade off between space saving and
>> future headaches :-)
>
> So you are saying NODES_SHIFT=8 and NR_CPUS=4k is what should be default
> given "sane" upper limits as of today?
Yup those seem sane in my opinion and amounts to a decent chunk of
space saved.
> I did hope for SHIFT 6 & NR=2k. Not sure this is worth fighting for.
We leave a little buffer for insanity ;-)
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-02-27 16:04 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
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 [this message]
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=6be36f62-91bb-4876-8ac5-4ebc4a4a7746@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