Lines Matching defs:dirty
181 * format structures. If the item has previously been logged and has dirty
183 * reducing the size of the relogged item by the amount of dirty data tracked
230 * dirty bits in. This will only be greater than one when we have a
231 * compound buffer with more than one segment dirty. Hence for compound
232 * buffers we need to track which segment the dirty bits correspond to,
288 * the actual size of the dirty bitmap rather than the size of the in
296 * If the map is not be dirty in the transaction, mark
649 bool dirty;
657 * If the bli is dirty and non-aborted, the buffer was clean in the
663 dirty = bip->bli_flags & XFS_BLI_DIRTY;
664 if (dirty && !aborted)
669 * regardless of dirty state. For example, consider an aborted
670 * transaction that invalidated a dirty bli and cleared the dirty
680 * Release the buffer associated with the buf log item. If there is no dirty
709 bool dirty = bip->bli_flags & XFS_BLI_DIRTY;
717 * The bli dirty state should match whether the blf has logged segments
718 * except for ordered buffers, where only the bli should be dirty.
720 ASSERT((!ordered && dirty == xfs_buf_item_dirty_format(bip)) ||
721 (ordered && dirty && !xfs_buf_item_dirty_format(bip)));
756 * We always re-log all the dirty data in a buffer, so usually the
873 "buffer item dirty bitmap (%u uints) too small to reflect %u bytes!",
892 * Mark bytes first through last inclusive as dirty in the buf
976 * Mark bytes first through last inclusive as dirty in the buf
991 * walk each buffer segment and mark them dirty appropriately.