From: Luis Chamberlain <mcgrof@kernel.org>
To: vincent.fu@samsung.com, fio@vger.kernel.org
Cc: mcgrof@kernel.org
Subject: [PATCH 0/2] fio: steady state for latency
Date: Thu, 24 Jul 2025 23:17:46 -0700 [thread overview]
Message-ID: <20250725061748.2180898-1-mcgrof@kernel.org> (raw)
I've been testing Claude Code for things lately, I figured one good task
may be to try steady state latency support which we lack support for. It
also fixed a small build bug.
Luis Chamberlain (2):
configure: libnfs + gnutls
fio: add latency steady state detection
HOWTO.rst | 12 +++++
client.c | 1 +
configure | 4 +-
example_latency_steadystate.fio | 47 ++++++++++++++++++++
options.c | 26 ++++++++++-
stat.h | 10 +++++
steadystate.c | 78 ++++++++++++++++++++++++++++-----
steadystate.h | 7 +++
8 files changed, 170 insertions(+), 15 deletions(-)
create mode 100644 example_latency_steadystate.fio
--
2.47.2
next reply other threads:[~2025-07-25 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 6:17 Luis Chamberlain [this message]
2025-07-25 6:17 ` [PATCH 1/2] configure: libnfs + gnutls Luis Chamberlain
2025-07-25 17:44 ` Vincent Fu
2025-07-25 6:17 ` [PATCH 2/2] fio: add latency steady state detection Luis Chamberlain
2025-07-28 18:14 ` Vincent Fu
2025-07-28 21:27 ` Sitsofe Wheeler
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=20250725061748.2180898-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=fio@vger.kernel.org \
--cc=vincent.fu@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox