From: Harry Yoo <harry@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: paulmck@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Hao Li <hao.li@linux.dev>, Uladzislau Rezki <urezki@gmail.com>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-mm@kvack.org, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/slab: stop exporting kvfree_rcu_barrier[_on_cache]()
Date: Mon, 3 Aug 2026 12:26:55 +0000 [thread overview]
Message-ID: <anCCVU7Y6lMaPmAT@dev> (raw)
In-Reply-To: <c4057657-7246-48ce-80d0-123e351a921b@kernel.org>
On Mon, Aug 03, 2026 at 09:59:44AM +0200, Vlastimil Babka (SUSE) wrote:
> On 7/30/26 22:59, Paul E. McKenney wrote:
> > On Thu, Jul 30, 2026 at 04:32:46PM +0200, Vlastimil Babka (SUSE) wrote:
> > Which reminds me... Are you guys interested in taking the kfree_rcu()
> > test code from kernel/rcu/rcuscale.c? See for example the kfree_rcu_test
> > module parameter.
>
> Hmm, we have a slub kunit test, but I think no such torture/scaling test
> infra. Maybe once we have that? What do you think, Harry?
That'd be definitely useful. We have been reviving performance tests
every time we wondered if it'd affect performance in a surprising way.
But we've never put that in the mainline ;)
Probably test_kmalloc_nolock_and_friends*() don't even belong
slub_kunit.
Perhaps worth starting small with lib/test_slab.c, and slowly
move/add torture/scaling tests to there?
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2026-08-03 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 14:32 [PATCH] mm/slab: stop exporting kvfree_rcu_barrier[_on_cache]() Vlastimil Babka (SUSE)
2026-07-30 20:59 ` Paul E. McKenney
2026-08-03 7:59 ` Vlastimil Babka (SUSE)
2026-08-03 12:26 ` Harry Yoo [this message]
2026-08-03 15:37 ` Paul E. McKenney
2026-08-01 12:51 ` Harry Yoo
2026-08-03 8:01 ` Vlastimil Babka (SUSE)
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=anCCVU7Y6lMaPmAT@dev \
--to=harry@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=hao.li@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=urezki@gmail.com \
--cc=vbabka@kernel.org \
/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.