Lines Matching refs:btt
23 \title{\texttt{btt} User Guide}
32 \texttt{btt} is a post-processing tool for the block layer IO tracing
43 IO rates and the like. \texttt{btt} goes further and produces a variety
48 This document will discuss \texttt{btt} usage, provide some sample output,
50 by the \texttt{btt} utility.
60 This document refers to the output formats generated by \texttt{btt}
68 The simple pipeline to get going with \texttt{btt} is to perform the
74 btt does not work in live mode.
78 will use \texttt{btt} with -- section~\ref{sec:o-D} shows how you
79 can dictate which devices to use with btt). If blkrawverify finds
81 -- utilizing \texttt{btt} on \emph{unclean} trace files produces
85 helps to ensure data coming from \texttt{btt} makes the most sense.
96 \item Run \texttt{btt} specifying the file produced by
97 \texttt{blkparse} utilizing the \texttt{-i} option (e.g.: \texttt{btt
104 The major default areas of output provided by \texttt{btt}
141 btt to refer to issue traces. Note that an I is used to refer to
160 work in \texttt{btt} is to better understand the multiplex nature of
325 handled. To determine this, \texttt{btt} keeps track of how many Q
351 to \texttt{btt} further sections are output:
382 \item[Per Device] Similar to the per-process display, \texttt{btt}
446 files which can be generated by btt. These include:
455 \item[iostat] iostat-like data can be distilled by btt, and is
522 to adjust btt's notion of what constitutes activity.
599 \texttt{btt} attempts to produce the results from running an
621 \texttt{btt} can produce a text file containing time line data for each
678 The latency data files which can be optionally produced by \texttt{btt}
689 \texttt{btt} can also produce two data files containing all IO-to-IO sector
767 will trigger \texttt{btt} to output seeks-per-second information. The
772 \texttt{btt} will just output the time value for the point, and the
802 Usage: btt 2.08
835 When specified on the command line, this directs btt to calculate
837 and the start of the next. By default \texttt{btt} uses the concept
843 Normally \texttt{btt} will not print out verbose information
869 Section~\ref{sec:activity} discussed how \texttt{btt} outputs a file
878 Normally, \texttt{btt} will produce data for all devices detected in
887 Likewise, \texttt{btt} will produce data for all processes (executables)
900 Specifies the binary input file that \texttt{btt} will interpret traces
906 This option triggers \texttt{btt} to generate iostat-like output to the
912 This option instructs \texttt{btt} to generate the D2C latency file
923 Tells \texttt{btt} to output seeks per second information. Each device
939 Normally \texttt{btt} sends the statistical output (covered in
945 This option tells \texttt{btt} to generate the per IO dump file as
956 This option instructs \texttt{btt} to generate the Q2C latency file
961 This option tells \texttt{btt} to generate a data file (using the given
973 This option instructs \texttt{btt} to generate the seek data file
979 interval, likewise, \texttt{btt} allows one to specify how many seconds
981 about the iostat-like capabilities of \texttt{btt} may be found in
988 \emph{This \texttt{btt} capability is still under construction, results are
992 These options allow one to dictate to \texttt{btt} when to start and stop
999 This option instructs \texttt{btt} to generate a data file containing
1024 Prints out the \texttt{btt} version, and exits.
1028 While \texttt{btt} is processing data, it will put out periodic (1-second
1038 # btt -i bp.bin -o btt -v
1055 then \texttt{btt} will generate this file.
1113 This option instructs \texttt{btt} to generate the Q2D latency file
1147 output from btt. If no <files> are specified, it will
1148 utilize all files generated after btt was run with -B
1169 \newpage\section{\label{sec:appendix}Sample \texttt{btt}
1171 Here is a complete output file from a btt run, illustrating a lot of the
1172 capabilities of btt.
1173 \input{sample-btt-output.tex}
