Lines Matching refs:traces

41 form of multiple individual traces per IO executed during the traced
73     parameters you want. You must save the traces to disk in this step,
94     files into one time-ordered stream of traces for all devices.
141       btt to refer to issue traces. Note that an I is used to refer to
142       \emph{insert} traces.}.
154       \item \emph{Q2Q} which measures the time between queue traces
162       = {Q2C}$ however, typically there are multiple queue traces that
354   \item[Per Process] As traces are emitted, they are tagged with the
358   provided which breaks down the traces according to process ID (name).
364   or kjournald for example). Similarly, completion traces are rarely
479   those periods of time when queue and complete traces are being
528     in either queue or completion traces across all devices.
531     being traced, that request queues Q and C traces are presented.
626     \item queue traces
627     \item get request traces
628     \item insert traces
629     \item merge traces
630     \item issue traces
631     \item completion traces
632     \item remap traces
639   stream. The issue and completion traces are replicated per IO.
870   containing Q and C activity, the notion of \emph{active} traces simply
871   means that there are Q or C traces occurring within a certain period
879   the traces parsed. With this option, one can reduce the analysis to
888   found in the traces. With this option, one can specify which processes
900   Specifies the binary input file that \texttt{btt} will interpret traces
969   Ignore remap traces; older kernels did not implement the full remap PDU.
1000   histogram information for \emph{unplug} traces on a per device
1030   input trace stream. The value describes how many traces have been
1031   processed. At the end of the run, the overall number of traces, trace
1032   rate (number of thousands of traces per second), and the real time for
1045 4581291 traces @ 279.7 Ktps