[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aS69Csa1gtztGl5e@hyeyoo>
Date: Tue, 2 Dec 2025 19:18:50 +0900
From: Harry Yoo <harry.yoo@...cle.com>
To: Jon Hunter <jonathanh@...dia.com>
Cc: surenb@...gle.com, Liam.Howlett@...cle.com, atomlin@...mlin.com,
bpf@...r.kernel.org, cl@...two.org, da.gomez@...nel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-modules@...r.kernel.org, lucas.demarchi@...el.com,
maple-tree@...ts.infradead.org, mcgrof@...nel.org, petr.pavlu@...e.com,
rcu@...r.kernel.org, rientjes@...gle.com, roman.gushchin@...ux.dev,
samitolvanen@...gle.com, sidhartha.kumar@...cle.com, urezki@...il.com,
vbabka@...e.cz,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH V1] mm/slab: introduce kvfree_rcu_barrier_on_cache() for
cache destruction
On Tue, Dec 02, 2025 at 09:29:17AM +0000, Jon Hunter wrote:
>
> 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@...e.cz>
> > Signed-off-by: Harry Yoo <harry.yoo@...cle.com>
> > ---
>
> Thanks for the rapid fix. I have been testing this and can confirm that this
> does fix the performance regression I was seeing.
Great!
> BTW shouldn't we add a 'Fixes:' tag above? I would like to ensure that this
> gets picked up for v6.18 stable.
Good point, I added Cc: stable and Fixes: tags.
(and your and Daniel's Reported-and-tested-by: tags)
> Otherwise ...
>
> Tested-by: Jon Hunter <jonathanh@...dia.com>
Thank you Jon and Daniel a lot for reporting regression and testing the fix!
--
Cheers,
Harry / Hyeonggon
Powered by blists - more mailing lists