From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: linux-btrace@vger.kernel.org
Subject: [PATCH] blkparse: man - Elaborate definitions of RWBS fields.
Date: Tue, 15 Aug 2017 21:17:52 +0000 [thread overview]
Message-ID: <20170815211752.9643-1-rgoldwyn@suse.de> (raw)
The RWBS fields can output more fields, which need detailed description.
This information is extracted from fill_rwbs() function. If there is more
to it, I'd be happy to include it.
I did not see Barrier Operations in the fill_rwbs() function. Also,
Flush and FUA have the same code, F. Besides, I am not sure if the N
field's description is correct.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
diff --git a/doc/blkparse.1 b/doc/blkparse.1
index be9b34b..fb70318 100644
--- a/doc/blkparse.1
+++ b/doc/blkparse.1
@@ -413,10 +413,32 @@ Split
.SH "RWBS DESCRIPTION"
-This is a small string containing at least one character ('R' for read, 'W'
-for write, or 'D' for block discard operation), and optionally either
-a 'B' (for barrier operations) or 'S' (for synchronous operations).
+This is a small string containing at least one character for the operation(s)
+performed. It is described by the following table:
+.IP R
+Read
+
+.IP W
+Write
+
+.IP D
+Discard Block
+
+.IP S
+Synchronous
+
+.IP N
+Nil or Nothing, a place holder.
+
+.IP F
+Flush or Force Unit Access (FUA)
+
+.IP A
+Read-Ahead
+
+.IP M
+Metadata
.SH "DEFAULT OUTPUT"
next reply other threads:[~2017-08-15 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 21:17 Goldwyn Rodrigues [this message]
2017-08-16 2:31 ` [PATCH] blkparse: man - Elaborate definitions of RWBS fields Goldwyn Rodrigues
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=20170815211752.9643-1-rgoldwyn@suse.de \
--to=rgoldwyn@suse.de \
--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