From: Hiroaki Mihara <hmihara@redhat.com>
To: linux-btrace@vger.kernel.org
Subject: [PATCH] blkparse: man: add absolute timestamp printing option
Date: Fri, 20 Sep 2019 05:03:36 +0000 [thread overview]
Message-ID: <20190920050336.16191-1-hmihara@redhat.com> (raw)
The functionality of printing out absolute timestamps has been
implemented in code but not documented in man pages.
When comparing the timings of related events with block I/O traces,
the absolute timestams play a key role. I think that the
documentation of this might be beneficial to blktrace users.
The related commit was done in 2006 as follows,
> commit 7bd4fd0a4fca645bb50a641afac1e460a4e32dfd
> Author: Olaf Kirch <okir@lst.de>
> Date: Fri Dec 1 10:34:11 2006 +0100
>
> [PATCH] Add timestamp support
>
> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
>
URL of the above patch,
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/blktrace.git/commit/?id{d4fd0a4fca645bb50a641afac1e460a4e32dfd
Signed-off-by: Hiroaki Mihara <hmihara@redhat.com>
---
doc/blkparse.1 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/blkparse.1 b/doc/blkparse.1
index 627b7b1..e494b6e 100644
--- a/doc/blkparse.1
+++ b/doc/blkparse.1
@@ -368,6 +368,9 @@ Elapsed value in microseconds (\fI\-t\fR command line option)
.IP \fBU\fR 4
Payload unsigned integer
+.IP \fBz\fR 4
+The absolute time, as local time in your time zone, with no date displayed
+
.PP
Note that the user can optionally specify field display width, and optionally a
left-aligned specifier. These precede field specifiers, with a '%' character,
--
2.21.0
next reply other threads:[~2019-09-20 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 5:03 Hiroaki Mihara [this message]
2019-09-24 21:14 ` [PATCH] blkparse: man: add absolute timestamp printing option Jeff Moyer
2019-09-24 21:29 ` Jens Axboe
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=20190920050336.16191-1-hmihara@redhat.com \
--to=hmihara@redhat.com \
--cc=linux-btrace@vger.kernel.org \
/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