Lines Matching refs:One
47 To build these tools, one needs to
62 one is able to \emph{replay} the IO again on the same machine or another
72 thus, to save system resources (including storage for traces), one could
144 in one bunch -- only IOs within the time specified are eligible
151 more than 8 individual IOs. With this option, one can increase or
156 Each input data file (one per device per CPU) results in a new record
157 data file (again, one per device per CPU) which contains information
159 these record data files by spawning a new pair of threads per file. One
173 \texttt{--cpus} option allows one to state how many CPUs on the replay
200 One idea to reduce errors in this area would be to push the IO replay
208 \texttt{--max-pkts} option). One \emph{could} simply specify
220 on one machine to devices (with offsets and sizes) on the replay
223 than one device, and could be utilized in case the replay device is
226 \medskip\emph{One could also add in the notion of CPU mappings as well --
305 amount of time (in nanoseconds) to include in any one bunch of IOs that
307 IOs processed at one time -- perhaps yielding in more realistic replay.
478 An example file for when one would map devices \texttt{/dev/sda} and
529 actually \emph{write} to devices one must explicitly specify the
