HomeSort by relevance Sort by last modified time
    Searched refs:IOs (Results 1 - 3 of 3) sorted by null

  /external/blktrace/btreplay/doc/
btreplay.tex 66 The basic operating work-flow to replay IOs would be something like:
70 device or devices that you wish to trace and later replay IOs upon. Note:
88 attempts to generate the same IOs seen during the sample workload phase.
95 \item[Device] The IOs are replayed on the same device as was seen
106 IOs during the sample workload. \texttt{btreplay} \emph{attempts} to
107 maintain the same time differential between IOs, but no guarantees as
110 \item[Device IO Stream Ordering] All IOs on a device are submitted in
114 As noted above, the time between IOs may not be accurately maintained
115 during replays. In addition the actual ordering of IOs \emph{between}
122 thread handles all IOs across all devices. This approach, whil
    [all...]
  /external/blktrace/btt/doc/
btt.tex 44 of overall statistics about each of the individual handling of IOs, and
108 \item[average component times across all IOs] The time line of each IO
155 in the system. This provides some idea as to how quickly IOs are
159 of IOs during the run\footnote{One of the areas that needs some
161 IOs during a run. In theory, one would like ${Q2I} + {I2D} + {D2C}
185 \emph{Q2A} and \emph{Q2C} times for those IOs.
215 requests into fewer, but larger, IOs to the underlying driver. In this
218 for the minimum, average and maximum IOs generated.
236 -- issued} IOs. The next two sections provides some rudimentary
238 between IOs. Values provided include the number of seeks (number of IO
    [all...]
  /external/fio/tools/
genfio 43 -c : Enable cached-based IOs

Completed in 77 milliseconds