From: Jens Axboe <axboe@kernel.dk>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
fio@vger.kernel.org, Vincent Fu <vincentfu@gmail.com>
Cc: Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH 0/9] introduce the log_issue_time option
Date: Wed, 28 Aug 2024 11:06:35 -0600 [thread overview]
Message-ID: <d056a445-52c3-4407-b792-fdd2b6be204e@kernel.dk> (raw)
In-Reply-To: <20240827070850.947037-1-shinichiro.kawasaki@wdc.com>
On 8/27/24 1:08 AM, Shin'ichiro Kawasaki wrote:
> When write_lat_log option is set, fio outputs the 'clat' completion
> latency log file. This clat log can be used to analyze IO latency. This
> file can also be considered as an IO trace file as each IO entry can
> fully describe an IO when the --log_offset and --log_prio options are
> also used. However, using the clat log file as an IO trace is inaccurate
> because the time field of each entry uses millisecond units, which is
> too coarse for fast IOs (e.g. when using SSDs). This series proposes the
> new option 'log_issue_time' to address the inaccuracy problem. When this
> option is set, fio adds another field to the log file entries to log an
> IO issuing time in nanoseconds.
>
> The first four patches in the series clean up the current code as
> preparation. The 5th patch introduces the 'log_issue_time' option. The
> following two patches document the new option. The last two patches add
> two test cases to check the log file format.
In general this looks fine, and I think it's a useful feature. However,
should we have an option to make the generic time in the log entry be
in nsec as well?
--
Jens Axboe
next prev parent reply other threads:[~2024-08-28 17:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 7:08 [PATCH 0/9] introduce the log_issue_time option Shin'ichiro Kawasaki
2024-08-27 7:08 ` [PATCH 1/9] stat: reduce arguments of add_*lat_sample() functions Shin'ichiro Kawasaki
2024-08-27 7:08 ` [PATCH 2/9] stat: reduce arguments of add_log_sample() Shin'ichiro Kawasaki
2024-08-27 7:08 ` [PATCH 3/9] iolog: refactor flush_samples() Shin'ichiro Kawasaki
2024-08-28 16:56 ` Nick Neumann
2024-08-29 5:44 ` Shinichiro Kawasaki
2024-08-27 7:08 ` [PATCH 4/9] iolog: drop struct io_sample_offset Shin'ichiro Kawasaki
2024-08-27 7:08 ` [PATCH 5/9] introduce the log_issue_time option Shin'ichiro Kawasaki
2024-08-28 17:02 ` Jens Axboe
2024-08-29 5:50 ` Shinichiro Kawasaki
2024-08-28 17:38 ` Nick Neumann
2024-08-29 1:05 ` Damien Le Moal
2024-08-29 1:44 ` Nick Neumann
2024-08-29 8:13 ` Shinichiro Kawasaki
2024-08-27 7:08 ` [PATCH 6/9] doc: fix the descriptions of the log_prio option Shin'ichiro Kawasaki
2024-08-27 7:08 ` [PATCH 7/9] doc: describe the log_issue_time option Shin'ichiro Kawasaki
2024-08-27 7:08 ` [PATCH 8/9] t/jobs/t0033: add test for the log file format Shin'ichiro Kawasaki
2024-08-28 18:46 ` Vincent Fu
2024-08-29 7:04 ` Shinichiro Kawasaki
2024-08-27 7:08 ` [PATCH 9/9] t/jobs/t0034: add test for the log_issue_time option Shin'ichiro Kawasaki
2024-08-28 18:47 ` Vincent Fu
2024-08-28 17:06 ` Jens Axboe [this message]
2024-08-29 0:59 ` [PATCH 0/9] introduce " Damien Le Moal
2024-08-29 1:49 ` Nick Neumann
2024-08-29 8:40 ` Shinichiro Kawasaki
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=d056a445-52c3-4407-b792-fdd2b6be204e@kernel.dk \
--to=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=fio@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--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