From: Edward Shishkin <edward@redhat.com>
To: linux-btrace@vger.kernel.org
Subject: [patch 6/6] blktrace: btt documentation update
Date: Fri, 30 Jul 2010 14:05:15 +0000 [thread overview]
Message-ID: <4C52DC1B.5030809@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 67 bytes --]
--
Edward O. Shishkin
Principal Software Engineer
Red Hat Czech
[-- Attachment #2: 13-blktrace-fix-595628.patch --]
[-- Type: text/plain, Size: 1433 bytes --]
Fixup for 595628.
Document btt options:
-m (--seeks-per-second);
-X (--easy-parse-avgs).
Signed-off-by: Edward Shishkin <edward@redhat.com>
---
--- blktrace-1.0.1.orig/doc/btt.1
+++ blktrace-1.0.1/doc/btt.1
@@ -30,6 +30,8 @@
.br
[ \-L <\fIfreq\fR> | \-\-periodic\-latencies=<\fIfreq\fR> ]
.br
+[ \-m <\fIoutput name\fR> | \-\-seeks\-per\-second=<\fIoutput name\fR> ]
+.br
[ \-M <\fIdev map\fR> | \-\-dev\-maps=<\fIdev map\fR>
.br
[ \-o <\fIoutput name\fR> | \-\-output\-file=<\fIoutput name\fR> ]
@@ -58,6 +60,8 @@
.br
[ \-V | \-\-version ]
.br
+[ \-X | \-\-easy\-parse\-avgs ]
+.br
[ \-z <\fIoutput name\fR> | \-\-q2d\-latencies=<\fIoutput name\fR> ]
@@ -199,6 +203,15 @@
an average latency is output -- a floating point value expressing seconds.
.RE
+.B \-m <\fIoutput name\fR>
+.br
+.B \-\-seeks\-per\-second=<\fIoutput name\fR>
+.RS 4
+Trigger btt to output seeks-per-second information. The first column will
+contain a time value (seconds), and the second column will indicate the
+number of seeks per second at that point.
+.RE
+
.B \-M <\fIdev map\fR>
.br
.B \-\-dev\-maps=<\fIdev map\fR>
@@ -330,6 +343,14 @@
Requests a more verbose output.
.RE
+.B \-X
+.br
+.B \-\-easy\-parse\-avgs
+.RS 4
+Provide data in an easy-to-parse form and write it to a file
+with .avg exentsion
+.RE
+
.B \-z <\fIoutput name\fR>
.br
.B \-\-q2d\-latencies=<\fIoutput name\fR>
next reply other threads:[~2010-07-30 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 14:05 Edward Shishkin [this message]
2010-07-30 14:38 ` [patch 6/6] blktrace: btt documentation update Alan D. Brunelle
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=4C52DC1B.5030809@redhat.com \
--to=edward@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.