From: David Rientjes <rientjes@google.com>
To: Usama Anjum <usama.anjum@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@gentwo.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Sarthak Sharma <sarthak.sharma@arm.com>,
"David Hildenbrand (Arm)" <david@kernel.org>
Subject: Re: [patch 0/3] lib: add synthetic MM benchmarks
Date: Fri, 11 Sep 2026 18:05:22 -0700 (PDT) [thread overview]
Message-ID: <1af513dc-a33b-9c7c-2827-097e16eac077@google.com> (raw)
In-Reply-To: <8936784e-9ccb-4c33-9b30-f99552e10f87@arm.com>
On Thu, 10 Sep 2026, Usama Anjum wrote:
> >> I thought about the same and just followed what appears to be the standard
> >> convention (like test_vmalloc above) for lib/ for now. If they should all
> >> be moved under tools/ somewhere, perhaps we handle that in a separate
> >> series?
> >
> > Yes. lib/ is just absolutely the wrong place for that.
> >
> > Maybe lib/tests/mm
> >
> > But then, I wonder if they could just be somewhere in tests/ directly ...
> >
> > Anyhow, it was also raised whether some of these could be written as kunit
> > tests. It's been a long time since I worked on these, so just mentioning it.
>
> I also think it would be best to try to add them as kunit. I'm not exactly sure if
> kunit would accept such benchmark kind of code. Some research is required there.
>
Sounds good, I'll transition these to kunit tests, move to mm/tests/
alongside the other MM kunit test, and send a v3 for just the vmstat test
as a separate thread. If all looks good, I can do this for slab and
pgalloc as well as a follow-up step.
prev parent reply other threads:[~2026-09-12 1:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 4:26 [patch 0/3] lib: add synthetic MM benchmarks David Rientjes
2026-07-31 4:26 ` [patch 1/3] lib: test_vmstat: add synthetic benchmark for vm stats David Rientjes
2026-08-01 13:20 ` Usama Arif
2026-08-02 23:05 ` David Rientjes
2026-08-02 23:06 ` [patch v2] " David Rientjes
2026-08-07 15:33 ` David Rientjes
2026-08-21 23:52 ` David Rientjes
2026-08-22 0:56 ` SJ Park
2026-09-10 9:40 ` David Hildenbrand (Arm)
2026-07-31 4:26 ` [patch 2/3] lib: test_slab: add synthetic benchmark for slab David Rientjes
2026-07-31 4:27 ` [patch 3/3] lib: test_pagealloc: add synthetic benchmark for page allocator David Rientjes
2026-07-31 9:00 ` [patch 0/3] lib: add synthetic MM benchmarks David Hildenbrand (Arm)
2026-08-02 22:19 ` David Rientjes
2026-08-05 7:03 ` David Hildenbrand (Arm)
2026-09-10 9:38 ` David Hildenbrand (Arm)
2026-09-10 12:12 ` Usama Anjum
2026-09-12 1:05 ` David Rientjes [this message]
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=1af513dc-a33b-9c7c-2827-097e16eac077@google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=sarthak.sharma@arm.com \
--cc=usama.anjum@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox