Lines Matching refs:force

282 When we have a log synchronisation event, commonly known as a "log force",
331 checkpoints to be written into the log buffers in the case of log force heavy
421 force can be issued to force the dependent transaction to disk immediately.
451 using the existing log force mechanisms to execute synchronous forces.
463 synchronisation in the log force code so that we don't need to wait anywhere
464 else for such serialisation - it only matters when we do a log force.
466 The only remaining complexity is that a log force now also has to handle the
471 the log force code enables the current mechanism for issuing synchronous
473 force the log at the LSN of that transaction) and so the higher level code
554 a CIL push triggered by a log force, only that there is no waiting for the
559 they will be flushed by the periodic log force issued by the xfssyncd. This log
560 force will push the CIL to disk, and if the transaction subsystem stays idle,
563 whether this log force needs to be done more frequently than the current rate
662 that is run as part of the checkpoint commit and log force sequencing. The code
663 path that triggers a CIL flush (i.e. whatever triggers the log force) will enter
667 record write. As a result it needs a lock and a wait variable. Log force
674 (obtained through completion of a commit record write) while log force
752 	<next log force>