From: Julia Lawall <julia.lawall@inria.fr>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
RCU <rcu@vger.kernel.org>,
cocci@inria.fr
Subject: Re: [cocci] patch idea: convert trivial call_rcu users to kfree_rcu
Date: Mon, 27 May 2024 10:13:40 +0200 (CEST) [thread overview]
Message-ID: <6b7e3ed9-d974-cb3b-6839-a6b7cf5f5a36@inria.fr> (raw)
In-Reply-To: <68b85796-c674-4691-936a-2051849f4692@suse.cz>
On Mon, 27 May 2024, Vlastimil Babka wrote:
> Hi,
>
> one bit from LSF/MM discussions is that there might be call_rcu users with a
> callback that only does a kmem_cache_free() to a specific cache. Since SLOB
> was removed, it's always ok to use kfree() and thus also kfree_rcu() on
> allocations from kmem_cache_alloc() in addition to kmalloc(). Thus, such
> call_rcu() users might be simplified to kfree_rcu(). I found some cases
> semi-manually, but I'd expect coccinelle could help here so if anyone wants
> to take this task, feel free to.
Thanks for the suggestion! I will try to look into it.
julia
next prev parent reply other threads:[~2024-05-27 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 7:46 Vlastimil Babka
2024-05-27 8:13 ` Julia Lawall [this message]
2024-05-27 19:27 ` [cocci] " Paul E. McKenney
2024-05-27 19:46 ` Uladzislau Rezki
2024-05-27 19:51 ` Julia Lawall
2024-05-27 20:36 ` Uladzislau Rezki
2024-05-27 20:43 ` Julia Lawall
2024-05-27 21:48 ` Paul E. McKenney
2024-05-28 5:09 ` Julia Lawall
2024-05-28 12:03 ` Uladzislau Rezki
2024-05-28 12:08 ` Julia Lawall
2024-05-28 13:21 ` Uladzislau Rezki
2024-05-28 14:29 ` Paul E. McKenney
2024-05-31 16:02 ` Julia Lawall
2024-06-03 17:25 ` Paul E. McKenney
2024-06-03 19:29 ` Vlastimil Babka
2024-06-03 19:51 ` Julia Lawall
2024-06-04 11:26 ` Uladzislau Rezki
2024-06-09 8:32 ` Julia Lawall
2024-06-09 10:00 ` Julia Lawall
2024-06-09 17:03 ` Paul E. McKenney
2024-06-11 16:40 ` Uladzislau Rezki
2024-06-11 17:25 ` Paul E. McKenney
2024-06-11 17:27 ` Uladzislau Rezki
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=6b7e3ed9-d974-cb3b-6839-a6b7cf5f5a36@inria.fr \
--to=julia.lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=linux-mm@kvack.org \
--cc=rcu@vger.kernel.org \
--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