Lines Matching refs:t

46 The method used to log an item or chain modifications together isn't
155 because it can't be written to the journal due to a lack of space in the
180 so that when we come to write the dirty metadata into the log we don't run out
235 into the log rather than basic blocks. Hence it technically isn't using LSNs to
353 hand in hand. That is, transactions don't get written to the physical journal
516 If we don't keep the vector around, we do not know where the region boundaries
696 dirty only the log item cachelines. Normally I wouldn't be concerned about one
753 synchronisation in the log force code so that we don't need to wait anywhere
770 transaction. We don't know how big a checkpoint transaction is going to be
840 As mentioned early, transactions can't grow to more than half the size of the
894 current CIL or not. If we don't pin the CIL first before we check and pin the
1079 behaviour, allocation or freeing that don't already exist.