From: Jon Hunter <jonathanh@nvidia.com>
To: Harry Yoo <harry.yoo@oracle.com>, surenb@google.com
Cc: Liam.Howlett@oracle.com, atomlin@atomlin.com,
bpf@vger.kernel.org, cl@gentwo.org, da.gomez@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-modules@vger.kernel.org, lucas.demarchi@intel.com,
maple-tree@lists.infradead.org, mcgrof@kernel.org,
petr.pavlu@suse.com, rcu@vger.kernel.org, rientjes@google.com,
roman.gushchin@linux.dev, samitolvanen@google.com,
sidhartha.kumar@oracle.com, urezki@gmail.com, vbabka@suse.cz,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V1] mm/slab: introduce kvfree_rcu_barrier_on_cache() for cache destruction
Date: Tue, 2 Dec 2025 09:29:17 +0000 [thread overview]
Message-ID: <be021cb8-9bff-4bfc-bc79-c84cbb3f4c4e@nvidia.com> (raw)
In-Reply-To: <20251128113740.90129-1-harry.yoo@oracle.com>
On 28/11/2025 11:37, Harry Yoo wrote:
> Currently, kvfree_rcu_barrier() flushes RCU sheaves across all slab
> caches when a cache is destroyed. This is unnecessary when destroying
> a slab cache; only the RCU sheaves belonging to the cache being destroyed
> need to be flushed.
>
> As suggested by Vlastimil Babka, introduce a weaker form of
> kvfree_rcu_barrier() that operates on a specific slab cache and call it
> on cache destruction.
>
> The performance benefit is evaluated on a 12 core 24 threads AMD Ryzen
> 5900X machine (1 socket), by loading slub_kunit module.
>
> Before:
> Total calls: 19
> Average latency (us): 8529
> Total time (us): 162069
>
> After:
> Total calls: 19
> Average latency (us): 3804
> Total time (us): 72287
>
> Link: https://lore.kernel.org/linux-mm/0406562e-2066-4cf8-9902-b2b0616dd742@kernel.org
> Link: https://lore.kernel.org/linux-mm/e988eff6-1287-425e-a06c-805af5bbf262@nvidia.com
> Link: https://lore.kernel.org/linux-mm/1bda09da-93be-4737-aef0-d47f8c5c9301@suse.cz
> Suggested-by: Vlastimil Babka <vbabka@suse.cz>
> Signed-off-by: Harry Yoo <harry.yoo@oracle.com>
> ---
Thanks for the rapid fix. I have been testing this and can confirm that
this does fix the performance regression I was seeing.
BTW shouldn't we add a 'Fixes:' tag above? I would like to ensure that
this gets picked up for v6.18 stable.
Otherwise ...
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Thanks!
Jon
--
nvpublic
next parent reply other threads:[~2025-12-02 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJuCfpFTMQD6oyR_Q1ds7XL4Km7h2mmzSv4z7f5fFnQ14=+g_A@mail.gmail.com>
[not found] ` <20251128113740.90129-1-harry.yoo@oracle.com>
2025-12-02 9:29 ` Jon Hunter [this message]
2025-12-02 10:18 ` [PATCH V1] mm/slab: introduce kvfree_rcu_barrier_on_cache() for cache destruction Harry Yoo
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=be021cb8-9bff-4bfc-bc79-c84cbb3f4c4e@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=Liam.Howlett@oracle.com \
--cc=atomlin@atomlin.com \
--cc=bpf@vger.kernel.org \
--cc=cl@gentwo.org \
--cc=da.gomez@kernel.org \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=maple-tree@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rcu@vger.kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=samitolvanen@google.com \
--cc=sidhartha.kumar@oracle.com \
--cc=surenb@google.com \
--cc=urezki@gmail.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