From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Amir Goldstein <amir73il@gmail.com>, Josef Bacik <josef@toxicpanda.com>
Cc: Hans Holmberg <Hans.Holmberg@wdc.com>,
"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>,
"jack@suse.com" <jack@suse.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] A common project for file system performance testing
Date: Fri, 13 Feb 2026 06:59:22 +0000 [thread overview]
Message-ID: <62ccce85-2f2e-479e-a1e2-b6821ef6b1f6@wdc.com> (raw)
In-Reply-To: <CAOQ4uxia_BDVOLLnuN=OzhpUYBdFkd10T+079h7+PjHXkt208w@mail.gmail.com>
On 2/12/26 6:37 PM, Amir Goldstein wrote:
> The fact that there is still a single test in fstests/tests/perf since 2017
> says it all - it's not about lack of tests to run, it is about lack of resources
> and this is not the sort of thing that gets resolved in LSFMM discussion IMO.
As sad as it might be, I'm afraid you're 100% correct on this.
next prev parent reply other threads:[~2026-02-13 6:59 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 [this message]
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
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=62ccce85-2f2e-479e-a1e2-b6821ef6b1f6@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Hans.Holmberg@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=amir73il@gmail.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 \
/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.