Lines Matching refs:Device
60 IO layer -- indicating the device, CPU number, time stamp, IO direction,
70 device or devices that you wish to trace and later replay IOs upon. Note:
95 \item[Device] The IOs are replayed on the same device as was seen
100 \item[IO offset] The same device offset is maintained.
110 \item[Device IO Stream Ordering] All IOs on a device are submitted in
116 devices is not necessarily maintained. (Each device with an IO stream
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
221 machine\footnote{The notion of an offset and device size to replay on
222 could be used to both allow for a single device to masquerade as more
223 than one device, and could be utilized in case the replay device is
224 smaller than the recorded device.}.}
227 device $D_{rec}$ managed by CPU $C_{rec}$ on the recorded system
228 shall be replayed on device $D_{rep}$ and CPU $C_{rep}$ on the
235 information on device mapping.
329 \item Device identifier (taken directly from the device name of the
362 \item[Field 1] The first field contains the device name and CPU
363 identifier. Thus: \texttt{sdab:0:} means the device \texttt{sdab} and
367 processed for each device file.
445 \item Device identifier (taken directly from the device name of the
464 Specify Device Mappings}
467 file containing device mappings. The file must be very simply managed, with
471 \item The device name on the recorded system (with the \texttt{'/dev/'}
474 \item The device name on the replay system to use (again, without the
