From: Gregory Price <gourry@gourry.net>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Cui Chao <cuichao1753@phytium.com.cn>,
dan.j.williams@intel.com, Mike Rapoport <rppt@kernel.org>,
Wang Yinfeng <wangyinfeng@phytium.com.cn>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, qemu-devel@nongnu.org,
"David Hildenbrand (Arm)" <david@kernel.org>
Subject: Re: [PATCH v2 1/1] mm: numa_memblks: Identify the accurate NUMA ID of CFMW
Date: Fri, 6 Feb 2026 11:32:09 -0500 [thread overview]
Message-ID: <aYYXif7IPXnXZPnn@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20260206162644.000050fe@huawei.com>
On Fri, Feb 06, 2026 at 04:26:44PM +0000, Jonathan Cameron wrote:
> >
> > This should fall out cleanly.
> >
> > The additional nodes won't be associated with anything, but could be
> > used for hotplug - I imagine.
> >
>
> That aligns with what I was thinking as a first solution to allowing this
> to be more dynamic. We can get clever later if this doesn't prove sufficient.
>
I can get this out pretty quickly, hopefully sometime next week.
I had a long talk with Dan about this topic previously, and I'm not sure
how we get more dynamic than this to be honest. nr_possible_nodes is
*definitely* expected to be immutable after __init all over the kernel,
it's used to allocate a memory.
Surface area is very large here.
~Gregory
next prev parent reply other threads:[~2026-02-06 16:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 3:10 [PATCH v2 0/1] " Cui Chao
2026-01-06 3:10 ` [PATCH v2 1/1] mm: numa_memblks: " Cui Chao
2026-01-08 16:19 ` Jonathan Cameron
2026-01-08 17:48 ` Andrew Morton
2026-01-15 9:43 ` Cui Chao
2026-01-15 18:18 ` Andrew Morton
2026-01-15 19:50 ` dan.j.williams
2026-01-22 8:03 ` Cui Chao
2026-01-22 21:28 ` Andrew Morton
2026-01-23 8:59 ` Cui Chao
2026-01-23 16:46 ` Gregory Price
2026-01-26 9:06 ` Cui Chao
2026-02-05 22:58 ` Andrew Morton
2026-02-05 23:10 ` Gregory Price
2026-02-06 11:03 ` Jonathan Cameron
2026-02-06 13:31 ` Gregory Price
2026-02-06 15:09 ` Jonathan Cameron
2026-02-06 15:53 ` Gregory Price
2026-02-06 16:26 ` Jonathan Cameron
2026-02-06 16:32 ` Gregory Price [this message]
2026-02-19 14:19 ` Jonathan Cameron
2026-02-06 15:57 ` Andrew Morton
2026-02-06 16:23 ` Jonathan Cameron
2026-01-09 9:35 ` Pratyush Brahma
2026-01-15 10:06 ` Cui Chao
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=aYYXif7IPXnXZPnn@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=cuichao1753@phytium.com.cn \
--cc=dan.j.williams@intel.com \
--cc=david@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qemu-devel@nongnu.org \
--cc=rppt@kernel.org \
--cc=wangyinfeng@phytium.com.cn \
/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