Lines Matching refs:As
8 % it under the terms of the GNU General Public License as published by
33 tool called blktrace. As noted in its Users Guide, blktrace
55 section~\ref{sec:cmd-line}), as we felt that discussing some of the
116 This is denoted as \emph{Q2I} time.
121 will see these listed as \texttt{S2G} times.}:
139 Referred to as \emph{I2D} time\footnote{The \emph{issue} trace
148 This is referred to as the \emph{D2C} time\
155 in the system. This provides some idea as to how quickly IOs are
170 (which are all presented in seconds), and overall count. As an
171 example\footnote{As with this display, the author has taken some liberty
190 as to where IO spend most of the time on average. The following output
258 number of seeks is indicative as to how many IOs are coming out of
354 \item[Per Process] As traces are emitted, they are tagged with the
407 time in seconds, as in:
524 The pairs are arranged as follows:
600 \texttt{iostat -x} command in parallel with the system as it is being
637 spaces). As an example, here is a snippet of 4 IOs that were merged
705 \item The prefix provided as the argument to the \texttt{-s} option.
753 \item[default] By default, the seek distance is calculated as the
844 concerning per-process and per-device data (as outlined in
895 Prints out the simple help information, as seen at the top of
945 This option tells \texttt{btt} to generate the per IO dump file as
962 name as a base) which contains: A time stamp in the first column,
1002 number of IOs released. There are 21 output values into the file, as
1017 The file name(s) generated use the text string passed as an argument for
1019 form, with a \texttt{.dat} extension (as an example, with \texttt{-u
