Home
last modified time | relevance | path

Searched refs:bunches (Results 1 – 2 of 2) sorted by relevance

/external/blktrace/btreplay/
Dbtrecord.c95 __u64 start_time, last_time, bunches, pkts; member
634 stream->bunches++; in stream_flush()
700 stream->bunches = stream->pkts = 0; in stream_open()
732 .nbunches = stream->bunches, in stream_close()
740 if (verbose && stream->bunches) { in stream_close()
747 (unsigned long long)stream->bunches, in stream_close()
748 (double)(stream->pkts) / (double)(stream->bunches)); in stream_close()
/external/blktrace/btreplay/doc/
Dbtreplay.tex139 time intervals between issues.}. To manage the size of the \emph{bunches},
158 about \emph{bunches} of IOs to be replayed. \texttt{btreplay} operates on
165 Each submitting thread simply reads the input file of \emph{bunches}
195 \item Lack of IO timing accuracy -- additional time between IO bunches.
351 sdab:0: 580661 pkts (tot), 126030 pkts (replay), 89809 bunches, 1.4 pkts/bunch
352 sdab:1: 2559775 pkts (tot), 430172 pkts (replay), 293029 bunches, 1.5 pkts/bunch
353 sdab:2: 653559 pkts (tot), 136522 pkts (replay), 102288 bunches, 1.3 pkts/bunch
354 sdab:3: 474773 pkts (tot), 117849 pkts (replay), 69572 bunches, 1.7 pkts/bunch
372 \item[Field 4] The fourth field contains the total number of IO bunches.