Searched refs:replayed (Results 1 – 8 of 8) sorted by relevance
110 Module replayed = Elements.getModule(elements); in testGetProviderAvailableAtInjectMembersTime() local111 Injector replayedInjector = Guice.createInjector(replayed); in testGetProviderAvailableAtInjectMembersTime()
65 - Resulting picture may be replayed multiple times
95 \item[Device] The IOs are replayed on the same device as was seen158 about \emph{bunches} of IOs to be replayed. \texttt{btreplay} operates on199 to guarantee per-IO timing accuracy with respect to other replayed IOs?228 shall be replayed on device $D_{rep}$ and CPU $C_{rep}$ on the498 ignored. IOs will be replayed without inter-bunch delays.503 While the \texttt{--no-stalls} option allows the traces to be replayed
72 This allows display lists to be replayed by the tnl module
1400 mapping. Replay_redirect causes all IOPS to be replayed onto1403 IO in the blktrace to be replayed onto /dev/sdc. This means1404 multiple devices will be replayed onto a single, if the trace1406 replayed concurrently to multiple redirected devices you must
339 the journal was replayed).775 which is marked as needing the journal replayed when the force ("-f")1434 replayed, and if the journal *was* being replayed, the "error bit"3555 record an undo log which can replayed by the program e2undo.5521 replayed when using an alternate superblock.6373 the external journal device if the journal needed to be replayed.
1675 replayed by the e2undo program.2740 replayed when using an alternate superblock.3195 trashed external journals needing to be replayed, e2fsck now hides