Lines Matching refs:That
12 % This program is distributed in the hope that it will be useful,
55 section~\ref{sec:cmd-line}), as we felt that discussing some of the
62 output formats prior to that.
77 all devices that were traced (or at least on all devices that you
84 While this step is optional, we have found that performing this
120 for a request. That occurs between the Q and G operations. You
127 \item[G2I] Time needed to put that request onto the request
131 For \emph{merged} requests -- an incoming request that is merged
141 btt to refer to issue traces. Note that an I is used to refer to
159 of IOs during the run\footnote{One of the areas that needs some
162 = {Q2C}$ however, typically there are multiple queue traces that
192 IO\footnote{It should be noted that incoming requests either go through:
228 we see that (on average) the block IO layer is combining upwards of
247 that are handled by underlying drivers.
256 that seeks tend to have an equal amount of forward and backwards
326 requests came in, and subtracts requests that have been issued (D).
360 One must be aware, however, that the process ID may not have anything
452 copied to another file that is \emph{more easily parsed.} Refer to
459 that shows each of the IO components on consecutive lines (rather
478 The activity data file contains a series of data values that indicate
519 What this indicates is that there was q activity for the system
531 being traced, that request queues Q and C traces are presented.
561 representing sizes $\ge 1024$ blocks. (This is done so that one can
565 column (Y values) represents the number of IOs of that size.
573 the 3 runs -- in particular, one can see that there is only a single
587 Y axis for this chart.}. Again, visually, one can see that the black
603 note that the line has been split to fit on the printed page:
616 Note that the STAMP field contains the runtime (in seconds) for that
637 spaces). As an example, here is a snippet of 4 IOs that were merged
685 command at that time (either Q2D, D2C or Q2C).
740 Figure~\ref{fig:seek} shows a simple graph that can be produced which
755 concept of \emph{closeness} means that it could either be the
769 will indicate the number of seeks per second at that point.
775 value is the number of seeks present at that time.
779 in that time frame, then:
845 section~\ref{sec:detailed-data}). If you desire that level of
871 means that there are Q or C traces occurring within a certain period
873 allowing one to change that granularity. The smaller the value, the
900 Specifies the binary input file that \texttt{btt} will interpret traces
919 average latency over that period.
950 The \texttt{-P} option will generate a file that contains a list of all IO
