From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
"Uladzislau Rezki (Sony)" <urezki@gmail.com>,
RCU <rcu@vger.kernel.org>
Subject: [GIT PULL] slab updates for 6.14
Date: Fri, 17 Jan 2025 15:13:18 +0100 [thread overview]
Message-ID: <3154387b-c045-401e-800c-f5d05be033e4@suse.cz> (raw)
Hi Linus,
please pull the latest slab updates from:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.14
There's a small conflict with the mm tree:
https://lore.kernel.org/all/20241216152721.15c5864d@canb.auug.org.au/
Thanks,
Vlastimil
======================================
* Move the kfree_rcu() implementation from RCU to SLAB subsystem
(Uladzislau Rezki)
The kfree_rcu() implementation has been historically maintained in the RCU
subsystem. At LSF/MM we agreed to move it to SLAB, where it more logically
belongs to. The batching is planned be more integrated with SLUB internals in
the future, while using the RCU APIs like any other subsystem.
* Fix for kernel-doc warning (Randy Dunlap)
----------------------------------------------------------------
Randy Dunlap (1):
mm/slab: fix kernel-doc func param names
Uladzislau Rezki (Sony) (5):
rcu/kvfree: Initialize kvfree_rcu() separately
rcu/kvfree: Move some functions under CONFIG_TINY_RCU
rcu/kvfree: Adjust names passed into trace functions
rcu/kvfree: Adjust a shrinker name
mm/slab: Move kvfree_rcu() into SLAB
Vlastimil Babka (1):
Merge branch 'slab/for-6.14/kfree_rcu_move' into slab/for-next
include/linux/slab.h | 1 +
init/main.c | 1 +
kernel/rcu/tree.c | 876 --------------------------------------------------
mm/slab.h | 4 +-
mm/slab_common.c | 880 +++++++++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 884 insertions(+), 878 deletions(-)
next reply other threads:[~2025-01-17 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 14:13 Vlastimil Babka [this message]
2025-01-20 17:54 ` Sasha Levin
2025-01-20 20:35 ` Vlastimil Babka
2025-01-21 23:53 ` Christoph Lameter (Ampere)
2025-01-22 0:24 ` Sasha Levin
2025-01-21 23:04 ` pr-tracker-bot
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=3154387b-c045-401e-800c-f5d05be033e4@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rcu@vger.kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=urezki@gmail.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