From: "Paul E. McKenney" <paulmck@kernel.org>
To: "Christoph Lameter (Ampere)" <cl@gentwo.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Sweet Tea Dorminy <sweettea@google.com>,
Mateusz Guzik <mjguzik@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Martin Liu <liumartin@google.com>,
David Rientjes <rientjes@google.com>,
christian.koenig@amd.com, Shakeel Butt <shakeel.butt@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Christian Brauner <brauner@kernel.org>,
Wei Yang <richard.weiyang@gmail.com>,
David Hildenbrand <david@redhat.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-mm@kvack.org, linux-trace-kernel@vger.kernel.org,
Yu Zhao <yuzhao@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [RFC PATCH v2] Introduce Hierarchical Per-CPU Counters
Date: Tue, 8 Apr 2025 14:46:53 -0700 [thread overview]
Message-ID: <077bfec0-c918-48b1-b133-36b4bba5d66a@paulmck-laptop> (raw)
In-Reply-To: <8897b4e1-b5ba-807d-7bc4-5a6080a93462@gentwo.org>
On Tue, Apr 08, 2025 at 02:21:59PM -0700, Christoph Lameter (Ampere) wrote:
> On Tue, 8 Apr 2025, Paul E. McKenney wrote:
>
> > RCU handles this by iterating from zero to nr_cpu_ids, which is set during
> > early boot. It also builds its tree-shaped data structures during early
> > boot based on nr_cpu_ids.
>
> nr_cpu_ids is better but there are funky things like the default bios of a
> major server vendor indicating 256 or so possible cpus although only 2
> were installed. Thus nr_cpu_id is 256. Presumably some hardware
> configurations can support onlining 256 cpus....
Indeed there are. So some portions of RCU build for nr_cpu_ids but
activate portions of the data structures (e.g., spawn kthreads) only
for those CPUs that actually come online at least once.
But should we really be optimizing to that degree for that sort of
breakage? Just extra data structure, who cares?
Yes, I do understand that the vendor in question, whoever it is, would
not consider their default BIOS to be broken. They are welcome to
their opinion. ;-)
Thanx, Paul
next prev parent reply other threads:[~2025-04-08 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 16:05 Mathieu Desnoyers
2025-04-08 16:37 ` Christoph Lameter (Ampere)
2025-04-08 17:01 ` Matthew Wilcox
2025-04-08 17:41 ` Liam R. Howlett
2025-04-08 19:40 ` Mathieu Desnoyers
2025-04-08 20:08 ` Liam R. Howlett
2025-04-08 19:29 ` Mathieu Desnoyers
2025-04-08 20:44 ` Christoph Lameter (Ampere)
2025-04-08 21:00 ` Paul E. McKenney
2025-04-08 21:21 ` Christoph Lameter (Ampere)
2025-04-08 21:46 ` Paul E. McKenney [this message]
2025-04-08 22:12 ` Roman Gushchin
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=077bfec0-c918-48b1-b133-36b4bba5d66a@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=christian.koenig@amd.com \
--cc=cl@gentwo.org \
--cc=david@redhat.com \
--cc=dennis@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=liumartin@google.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mjguzik@gmail.com \
--cc=richard.weiyang@gmail.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rostedt@goodmis.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=sweettea@google.com \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=yuzhao@google.com \
/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