From: Ankit Kumar <ankit.kumar@samsung.com>
To: axboe@kernel.dk, vincentfu@gmail.com
Cc: fio@vger.kernel.org, Ankit Kumar <ankit.kumar@samsung.com>
Subject: [PATCH 0/2] log both average and max values over the window
Date: Mon, 22 Jan 2024 16:52:58 +0530 [thread overview]
Message-ID: <20240122112300.47805-1-ankit.kumar@samsung.com> (raw)
In-Reply-To: CGME20240122060524epcas5p1ef9946a897a9a25b6b89072f01fdc924@epcas5p1.samsung.com
This series modifies option log_max_value to report average, max or both
the values. The log_max_value option type has been changed from boolean to
integer with min and max capped to 0 and 2 respectively. There is no
change to existing log formats while reporting only average or max values.
The fio documentation has been updated specifying the new log format
when both values are reported.
Ankit Kumar (2):
stat: log out both average and max over the window
docs: update fio man page for log_max_value
HOWTO.rst | 23 +++++++++++------
client.c | 6 +++--
fio.1 | 29 +++++++++++++++-------
iolog.c | 74 ++++++++++++++++++++++++++++++++++++++++---------------
iolog.h | 21 +++++++++++++---
options.c | 8 +++---
server.c | 6 +++--
stat.c | 32 ++++++++++++++----------
8 files changed, 140 insertions(+), 59 deletions(-)
--
2.25.1
next parent reply other threads:[~2024-01-22 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240122060524epcas5p1ef9946a897a9a25b6b89072f01fdc924@epcas5p1.samsung.com>
2024-01-22 11:22 ` Ankit Kumar [this message]
[not found] ` <CGME20240122060525epcas5p17d417303b27a454e1db288a61e0642fc@epcas5p1.samsung.com>
2024-01-22 11:22 ` [PATCH 1/2] stat: log out both average and max over the window Ankit Kumar
2024-01-22 18:17 ` Jens Axboe
2024-01-22 19:55 ` Vincent Fu
[not found] ` <CGME20240122060526epcas5p21030269f7690010a4cb98b7ce4e3b729@epcas5p2.samsung.com>
2024-01-22 11:23 ` [PATCH 2/2] docs: update fio man page for log_max_value Ankit Kumar
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=20240122112300.47805-1-ankit.kumar@samsung.com \
--to=ankit.kumar@samsung.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=vincentfu@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).