From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Hans Holmberg <Hans.Holmberg@wdc.com>, Theodore Tso <tytso@mit.edu>
Cc: "lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>, hch <hch@lst.de>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
"josef@toxicpanda.com" <josef@toxicpanda.com>,
"jack@suse.com" <jack@suse.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [LSF/MM/BPF TOPIC] A common project for file system performance testing
Date: Mon, 23 Feb 2026 13:26:45 +0000 [thread overview]
Message-ID: <5032694b-6b80-488f-bb2a-56fcabdc9847@wdc.com> (raw)
In-Reply-To: <660844a0-bf83-4d3a-8fec-84c02b678fef@wdc.com>
On 2/20/26 9:59 AM, Hans Holmberg wrote:
> Yeah, I think splitting things up in modules/parts would be really
> beneficial.
>
> Just like blktests and fstests mainly focus on providing good tests
> (with well defined ways for starting test runs and providing results),
> we could have a module or a project that just defines a bunch of useful
> workloads.
>
> Setting up benchmarking runs and analyzing & presenting results could
> be done by other modules as there'll be different preferences and needs
> for those, depending on use case, ci-system etc.
I know workload classification can be hard, but starting with a set of
fio scripts we can run would be a good start.
prev parent reply other threads:[~2026-02-23 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 13:42 [LSF/MM/BPF TOPIC] A common project for file system performance testing Hans Holmberg
2026-02-12 14:31 ` Daniel Wagner
2026-02-13 11:50 ` Shinichiro Kawasaki
2026-02-12 16:42 ` Johannes Thumshirn
2026-02-12 17:32 ` Josef Bacik
2026-02-12 17:37 ` [Lsf-pc] " Amir Goldstein
2026-02-12 19:03 ` Josef Bacik
2026-02-13 9:13 ` Hans Holmberg
2026-02-13 6:59 ` Johannes Thumshirn
2026-02-16 10:10 ` Jan Kara
2026-02-17 8:13 ` Hans Holmberg
2026-02-18 15:31 ` Theodore Tso
2026-02-20 8:59 ` Hans Holmberg
2026-02-23 13:26 ` Johannes Thumshirn [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=5032694b-6b80-488f-bb2a-56fcabdc9847@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Hans.Holmberg@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=tytso@mit.edu \
/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.