Lines Matching full:into
16 transaction reservations are structured and accounted, and then move into how we
161 available to write the modification into the journal before we start making
163 enough to take into account the amount of metadata that the change might need to
167 take into account all the hidden changes that might occur.
171 the extent into the inode's extent map might require a split of the extent map
180 so that when we come to write the dirty metadata into the log we don't run out
220 offset into the log. A LSN carries the cycle in the upper 32 bits and the
235 into the log rather than basic blocks. Hence it technically isn't using LSNs to
241 and need to write into the log. The reserve head is used to prevent new
350 metadata into the log.
464 Put simply, the current logging code formats the changes to each item into an
466 simply copies the memory these vectors point to into the log buffer during
471 If we then copy the vector into the memory buffer and rewrite the vector to
521 region state that needs to be placed into the headers during the log write.
544 double linked list. Items are inserted into this list during log buffer IO
572 all the items in the CIL must be written into the log via the log buffers.
602 code to write the changes into the log. To do this efficiently, we need to
614 those changes into the current checkpoint context. We then initialise a new
619 are formatting the checkpoint into the log. It also allows concurrent
620 checkpoints to be written into the log buffers in the case of log force heavy
625 To ensure that we can be writing an item into a checkpoint transaction at
627 into the new CIL, then checkpoint transaction commit code cannot use log items
628 to store the list of log vectors that need to be written into the transaction.
682 Once the checkpoint is written into the log buffers, the checkpoint context is
685 run transaction committed processing for the log items (i.e. insert into AIL
715 written into. While this works just fine for the existing transaction
717 written directly into the log buffers. Hence some other method of sequencing
828 result of a transaction commit inserting a new memory buffer into the CIL, then
881 insertion into the CIL, unpin on checkpoint completion". In other words, the
883 pin the object the first time it is inserted into the CIL - if it is already in
926 across the formatting of the objects into memory buffers (i.e. while memcpy()s
947 are inserted into the CIL. Because transactions can enter this code
957 an ordering loop after writing all the log vectors into the log buffers but
995 Format item into log buffer
996 Write commit LSN into transaction
1005 Insert log item into AIL
1006 Write commit LSN into log item
1026 With delayed logging, there are new steps inserted into the life cycle::
1040 Format item into log vector + buffer
1042 Insert log item into CIL
1043 Write CIL context sequence into transaction
1053 write log vectors into log
1062 Insert item into AIL
1063 Write commit LSN into log item