From: Oscar Salvador <osalvador@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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,
Oscar Salvador <osalvador@suse.de>
Subject: [PATCH v5 04/10] mm,slub: Use node-notifier instead of memory-notifier
Date: Thu, 5 Jun 2025 16:22:55 +0200 [thread overview]
Message-ID: <20250605142305.244465-5-osalvador@suse.de> (raw)
In-Reply-To: <20250605142305.244465-1-osalvador@suse.de>
slub is only concerned when a numa node changes its memory state,
so stop using the memory notifier and use the new numa node notifer
instead.
Signed-off-by: Oscar Salvador <osalvador@suse.de>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Harry Yoo <harry.yoo@oracle.com>
Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
---
mm/slub.c | 13 +++++--------
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
index f92b43d36adc..b8b5b81bfd1a 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -6164,8 +6164,8 @@ static int slab_mem_going_online_callback(void *arg)
{
struct kmem_cache_node *n;
struct kmem_cache *s;
- struct memory_notify *marg = arg;
- int nid = marg->status_change_nid;
+ struct node_notify *narg = arg;
+ int nid = narg->nid;
int ret = 0;
/*
@@ -6217,15 +6217,12 @@ static int slab_memory_callback(struct notifier_block *self,
int ret = 0;
switch (action) {
- case MEM_GOING_ONLINE:
+ case NODE_ADDING_FIRST_MEMORY:
ret = slab_mem_going_online_callback(arg);
break;
- case MEM_GOING_OFFLINE:
+ case NODE_REMOVING_LAST_MEMORY:
ret = slab_mem_going_offline_callback(arg);
break;
- case MEM_ONLINE:
- case MEM_CANCEL_OFFLINE:
- break;
}
if (ret)
ret = notifier_from_errno(ret);
@@ -6300,7 +6297,7 @@ void __init kmem_cache_init(void)
sizeof(struct kmem_cache_node),
SLAB_HWCACHE_ALIGN | SLAB_NO_OBJ_EXT, 0, 0);
- hotplug_memory_notifier(slab_memory_callback, SLAB_CALLBACK_PRI);
+ hotplug_node_notifier(slab_memory_callback, SLAB_CALLBACK_PRI);
/* Able to allocate the per node structures */
slab_state = PARTIAL;
--
2.49.0
next prev parent reply other threads:[~2025-06-05 14:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 14:22 [PATCH v5 00/10] 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 ` Oscar Salvador [this message]
2025-06-06 1:50 ` [PATCH v5 04/10] mm,slub: Use node-notifier instead of memory-notifier 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 ` [PATCH v5 00/10] Lorenzo Stoakes
2025-06-06 11:46 ` 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=20250605142305.244465-5-osalvador@suse.de \
--to=osalvador@suse.de \
--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=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