Lines Matching refs:committed

77 tracked via the transaction handle.  Once the transaction is committed, all
115 modification the loop made that was committed to the journal.
130 xfs_trans_commit() does not guarantee that the modification has been committed
136 that were committed prior to that change will also be seen.
139 ensuring that a long running permanent transaction is fully committed once it is
141 a "log force" to flush the outstanding committed transactions to stable storage
367 buffers are full and under IO, then no more transactions can be committed until
378 multiple times before they are committed to disk in the log buffers. If we
380 transactions A through D are committed to disk in the same log buffer.
538 to be the object that is used to track committed objects as it will always
552 such, we cannot reuse the AIL list pointers for tracking committed items, nor
554 committed item tracking needs its own locks, lists and state fields in the log
557 Similar to the AIL, tracking of committed items is done through a new list
559 committed and have formatted memory buffers attached to them. It tracks objects
618 committed items and effectively allows new transactions to be issued while we
685 run transaction committed processing for the log items (i.e. insert into AIL
706 committed transactions with the log sequence number of the transaction commit.
709 committed to the log. In the rare case that a dependent operation occurs (e.g.
731 checkpoint sequence needs to be committed before they can continue. As a
750 are also committed to disk before the one we need to wait for. Therefore we
864 that items get pinned once for every transaction that is committed to the log
1004 		Mark log item committed
1061 		Mark log item committed