From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Oscar Salvador <osalvador@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Harry Yoo <harry.yoo@oracle.com>, Rakie Kim <rakie.kim@sk.com>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 00/10]
Date: Fri, 6 Jun 2025 12:30:42 +0100 [thread overview]
Message-ID: <c4a96aa2-10ae-4dc1-abd8-be91f7e8b583@lucifer.local> (raw)
In-Reply-To: <20250605142305.244465-1-osalvador@suse.de>
Hi Oscar,
I don't have time to dig into what's broken here, but this series is breaking
the mm-new build.
NODE_REMOVED_LAST_MEMORY for instance doesn't seem to be defined, but there's a
bunch more errors.
Are you expecting stuff to land from other trees that isn't merged in Andrew's
tree yet? Maybe from slab tree?
We probably need to be careful with series that have dependencies like that
during the merge window, maybe RFC or wait until after merge window in that
case, or maybe add a note saying 'please don't merge to mm-new until after the
merge window' or something.
Thanks, Lorenzo
mm/slub.c: In function ‘slab_mem_going_online_callback’:
mm/slub.c:6168:23: error: invalid use of undefined type ‘struct node_notify’
6168 | int nid = narg->nid;
| ^~
mm/mempolicy.c: In function ‘wi_node_notifier’:
mm/mempolicy.c:3792:22: error: invalid use of undefined type ‘struct node_notify’
3792 | int nid = arg->nid;
| ^~
mm/slub.c: In function ‘slab_memory_callback’:
mm/slub.c:6220:14: error: ‘NODE_ADDING_FIRST_MEMORY’ undeclared (first use in this function)
6220 | case NODE_ADDING_FIRST_MEMORY:
| ^~~~~~~~~~~~~~~~~~~~~~~~
mm/slub.c:6220:14: note: each undeclared identifier is reported only once for each function it appears in
kernel/cgroup/cpuset.c: In function ‘cpuset_init_smp’:
kernel/cgroup/cpuset.c:4054:9: error: implicit declaration of function ‘hotplug_node_notifier’; did you mean ‘hotplug_memory_notifier’? [-Wimplicit-function-declaration]
4054 | hotplug_node_notifier(cpuset_track_online_nodes, CPUSET_CALLBACK_PRI);
| ^~~~~~~~~~~~~~~~~~~~~
| hotplug_memory_notifier
mm/mempolicy.c:3798:14: error: ‘NODE_ADDED_FIRST_MEMORY’ undeclared (first use in this function)
3798 | case NODE_ADDED_FIRST_MEMORY:
| ^~~~~~~~~~~~~~~~~~~~~~~
mm/mempolicy.c:3798:14: note: each undeclared identifier is reported only once for each function it appears in
mm/slub.c:6223:14: error: ‘NODE_REMOVING_LAST_MEMORY’ undeclared (first use in this function)
6223 | case NODE_REMOVING_LAST_MEMORY:
| ^~~~~~~~~~~~~~~~~~~~~~~~~
mm/slub.c: In function ‘kmem_cache_init’:
mm/slub.c:6300:9: error: implicit declaration of function ‘hotplug_node_notifier’; did you mean ‘hotplug_memory_notifier’? [-Wimplicit-function-declaration]
6300 | hotplug_node_notifier(slab_memory_callback, SLAB_CALLBACK_PRI);
| ^~~~~~~~~~~~~~~~~~~~~
| hotplug_memory_notifier
make[4]: *** [scripts/Makefile.build:203: kernel/cgroup/cpuset.o] Error 1
make[3]: *** [scripts/Makefile.build:461: kernel/cgroup] Error 2
make[2]: *** [scripts/Makefile.build:461: kernel] Error 2
make[2]: *** Waiting for unfinished jobs....
mm/mempolicy.c:3804:14: error: ‘NODE_REMOVED_LAST_MEMORY’ undeclared (first use in this function)
3804 | case NODE_REMOVED_LAST_MEMORY:
| ^~~~~~~~~~~~~~~~~~~~~~~~
mm/mempolicy.c: In function ‘add_weighted_interleave_group’:
mm/mempolicy.c:3843:9: error: implicit declaration of function ‘hotplug_node_notifier’; did you mean ‘hotplug_memory_notifier’? [-Wimplicit-function-declaration]
3843 | hotplug_node_notifier(wi_node_notifier, DEFAULT_CALLBACK_PRI);
| ^~~~~~~~~~~~~~~~~~~~~
| hotplug_memory_notifier
On Thu, Jun 05, 2025 at 04:22:51PM +0200, Oscar Salvador wrote:
> v4 -> v5:
> - Split out conversion for different consumers (per David)
> - Renamed node-notifier actions (per David)
> - Added new Documentation for new node-notifier and updated
> the memory-notifier one to reflect the changes
> - Make sure we do not trigger anything when !CONFIG_NUMA (per David)
>
> v3 -> v4:
> - Fix typos pointed out by Alok Tiwari
> - Further cleanups suggested by Vlastimil
> - Add RBs-by from Vlastimil
>
> v2 -> v3:
> - Add Suggested-by (David)
> - Replace last N_NORMAL_MEMORY mention in slub (David)
> - Replace the notifier for autoweitght-mempolicy
> - Fix build on !CONFIG_MEMORY_HOTPLUG
>
> v1 -> v2:
> - Remove status_change_nid_normal and the code that
> deals with it (David & Vlastimil)
> - Remove slab_mem_offline_callback (David & Vlastimil)
> - Change the order of canceling the notifiers
> in {online,offline}_pages (Vlastimil)
> - Fix up a couple of whitespaces (Jonathan Cameron)
> - Add RBs-by
>
> Memory notifier is a tool that allow consumers to get notified whenever
> memory gets onlined or offlined in the system.
> Currently, there are 10 consumers of that, but 5 out of those 10 consumers
> are only interested in getting notifications when a numa node changes its
> memory state.
> That means going from memoryless to memory-aware of vice versa.
>
> Which means that for every {online,offline}_pages operation they get
> notified even though the numa node might not have changed its state.
> This is suboptimal, and we want to decouple numa node state changes from
> memory state changes.
>
> While we are doing this, remove status_change_nid_normal, as the only
> current user (slub) does not really need it.
> This allows us to further simplify and clean up the code.
>
> The first patch gets rid of status_change_nid_normal in slub.
> The second patch implements a numa node notifier that does just that, and have
> those consumers register in there, so they get notified only when they are
> interested.
>
> The third patch replaces 'status_change_nid{_normal}' fields within
> memory_notify with a 'nid', as that is only what we need for memory
> notifer and update the only user of it (page_ext).
>
> Consumers that are only interested in numa node states change are:
>
> - memory-tier
> - slub
> - cpuset
> - hmat
> - cxl
> - autoweight-mempolicy
>
> Oscar Salvador (10):
> mm,slub: Do not special case N_NORMAL nodes for slab_nodes
> mm,memory_hotplug: Remove status_change_nid_normal and update
> documentation
> mm,memory_hotplug: Implement numa node notifier
> mm,slub: Use node-notifier instead of memory-notifier
> mm,memory-tiers: Use node-notifier instead of memory-notifier
> drivers,cxl: Use node-notifier instead of memory-notifier
> drivers,hmat: Use node-notifier instead of memory-notifier
> kernel,cpuset: Use node-notifier instead of memory-notifier
> mm,mempolicy: Use node-notifier instead of memory-notifier
> mm,memory_hotplug: Rename status_change_nid parameter in memory_notify
>
> Documentation/core-api/memory-hotplug.rst | 78 ++++++--
> .../zh_CN/core-api/memory-hotplug.rst | 3 -
> drivers/acpi/numa/hmat.c | 8 +-
> drivers/base/node.c | 21 +++
> drivers/cxl/core/region.c | 16 +-
> drivers/cxl/cxl.h | 4 +-
> include/linux/memory.h | 3 +-
> include/linux/node.h | 42 +++++
> kernel/cgroup/cpuset.c | 2 +-
> mm/memory-tiers.c | 14 +-
> mm/memory_hotplug.c | 167 ++++++++----------
> mm/mempolicy.c | 10 +-
> mm/page_ext.c | 12 +-
> mm/slub.c | 45 +----
> 14 files changed, 240 insertions(+), 185 deletions(-)
>
> --
> 2.49.0
>
>
>
next prev parent reply other threads:[~2025-06-06 11:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 14:22 Oscar Salvador
2025-06-05 14:22 ` [PATCH v5 01/10] mm,slub: Do not special case N_NORMAL nodes for slab_nodes Oscar Salvador
2025-06-05 14:22 ` [PATCH v5 02/10] mm,memory_hotplug: Remove status_change_nid_normal and update documentation Oscar Salvador
2025-06-05 14:34 ` Vlastimil Babka
2025-06-05 14:54 ` David Hildenbrand
2025-06-05 15:49 ` Oscar Salvador
2025-06-05 14:22 ` [PATCH v5 03/10] mm,memory_hotplug: Implement numa node notifier Oscar Salvador
2025-06-06 7:50 ` Oscar Salvador
2025-06-05 14:22 ` [PATCH v5 04/10] mm,slub: Use node-notifier instead of memory-notifier Oscar Salvador
2025-06-06 1:50 ` kernel test robot
2025-06-06 7:51 ` Oscar Salvador
2025-06-06 11:56 ` David Hildenbrand
2025-06-06 12:28 ` Oscar Salvador
2025-06-06 12:35 ` David Hildenbrand
2025-06-05 14:22 ` [PATCH v5 05/10] mm,memory-tiers: " Oscar Salvador
2025-06-06 11:50 ` David Hildenbrand
2025-06-05 14:22 ` [PATCH v5 06/10] drivers,cxl: " Oscar Salvador
2025-06-06 11:51 ` David Hildenbrand
2025-06-05 14:22 ` [PATCH v5 07/10] drivers,hmat: " Oscar Salvador
2025-06-06 11:51 ` David Hildenbrand
2025-06-07 22:59 ` Andrew Morton
2025-06-05 14:22 ` [PATCH v5 08/10] kernel,cpuset: " Oscar Salvador
2025-06-06 11:52 ` David Hildenbrand
2025-06-05 14:23 ` [PATCH v5 09/10] mm,mempolicy: " Oscar Salvador
2025-06-09 6:47 ` Rakie Kim
2025-06-05 14:23 ` [PATCH v5 10/10] mm,memory_hotplug: Rename status_change_nid parameter in memory_notify Oscar Salvador
2025-06-06 11:48 ` David Hildenbrand
2025-06-06 11:30 ` Lorenzo Stoakes [this message]
2025-06-06 11:46 ` [PATCH v5 00/10] David Hildenbrand
2025-06-06 12:31 ` Oscar Salvador
2025-06-06 12:45 ` Lorenzo Stoakes
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=c4a96aa2-10ae-4dc1-abd8-be91f7e8b583@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=42.hyeyoo@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=rakie.kim@sk.com \
--cc=vbabka@suse.cz \
/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