From: Uladzislau Rezki <urezki@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>,
"Christoph Lameter (Ampere)" <cl@gentwo.org>
Cc: "Christoph Lameter (Ampere)" <cl@gentwo.org>,
"Uladzislau Rezki (Sony)" <urezki@gmail.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, RCU <rcu@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: Re: [PATCH v2 0/5] Move kvfree_rcu() into SLAB (v2)
Date: Thu, 12 Dec 2024 20:13:45 +0100 [thread overview]
Message-ID: <Z1s16Vfa326d26h8@pc636> (raw)
In-Reply-To: <ab3c9f52-1643-4dfa-9a04-d6db4dfcf29a@paulmck-laptop>
On Thu, Dec 12, 2024 at 11:10:47AM -0800, Paul E. McKenney wrote:
> On Thu, Dec 12, 2024 at 10:30:28AM -0800, Christoph Lameter (Ampere) wrote:
> > On Thu, 12 Dec 2024, Uladzislau Rezki (Sony) wrote:
> >
> > > This is v2. It is based on the Linux 6.13-rc2. The first version is
> > > here:
> >
> > I do not see any use of internal slab interfaces by this code. It seems to
> > be using rcu internals though. So it would best be placed with the rcu
> > code.
>
> That is indeed the current state. The point of moving it is to later
> take advantage of internal slab state.
>
And, in fact we already have some integrations. For example a barrier
has been added for slab caches.
--
Uladzislau Rezki
next prev parent reply other threads:[~2024-12-12 19:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 18:02 [PATCH v2 0/5] Move kvfree_rcu() into SLAB (v2) Uladzislau Rezki (Sony)
2024-12-12 18:02 ` [PATCH v2 1/5] rcu/kvfree: Initialize kvfree_rcu() separately Uladzislau Rezki (Sony)
2024-12-12 18:02 ` [PATCH v2 2/5] rcu/kvfree: Move some functions under CONFIG_TINY_RCU Uladzislau Rezki (Sony)
2024-12-12 18:02 ` [PATCH v2 3/5] rcu/kvfree: Adjust names passed into trace functions Uladzislau Rezki (Sony)
2024-12-12 18:02 ` [PATCH v2 4/5] rcu/kvfree: Adjust a shrinker name Uladzislau Rezki (Sony)
2024-12-12 18:02 ` [PATCH v2 5/5] mm/slab: Move kvfree_rcu() into SLAB Uladzislau Rezki (Sony)
2024-12-12 18:30 ` [PATCH v2 0/5] Move kvfree_rcu() into SLAB (v2) Christoph Lameter (Ampere)
2024-12-12 19:08 ` Uladzislau Rezki
2024-12-12 19:10 ` Paul E. McKenney
2024-12-12 19:13 ` Uladzislau Rezki [this message]
2024-12-15 17:30 ` Vlastimil Babka
2024-12-15 18:21 ` Paul E. McKenney
2024-12-16 11:03 ` Uladzislau Rezki
2024-12-16 14:20 ` Vlastimil Babka
2024-12-16 15:41 ` Uladzislau Rezki
2024-12-16 15:44 ` Vlastimil Babka
2024-12-16 15:55 ` Uladzislau Rezki
2024-12-16 16:46 ` Paul E. McKenney
2025-01-20 22:06 ` Vlastimil Babka
2025-01-21 13:33 ` Uladzislau Rezki
2025-01-21 13:49 ` Vlastimil Babka
2025-01-21 14:14 ` Uladzislau Rezki
2025-01-21 20:32 ` Paul E. McKenney
2025-01-22 15:04 ` Joel Fernandes
2025-01-22 16:43 ` Vlastimil Babka
2025-01-22 16:47 ` Joel Fernandes
2025-01-22 17:42 ` Uladzislau Rezki
2024-12-16 13:07 ` Uladzislau Rezki
2025-01-11 19:40 ` Vlastimil Babka
2025-01-06 7:21 ` [External Mail] " Hyeonggon Yoo
2025-01-11 19:43 ` Vlastimil Babka
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=Z1s16Vfa326d26h8@pc636 \
--to=urezki@gmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleksiy.avramchenko@sony.com \
--cc=paulmck@kernel.org \
--cc=penberg@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.