Lines Matching defs:dirty
82 * initial count for a dirty buffer is 2 vectors - the format structure
83 * and the first dirty region.
131 * format structures. If the item has previously been logged and has dirty
133 * reducing the size of the relogged item by the amount of dirty data tracked
177 * dirty bits in. This will only be greater than one when we have a
178 * compound buffer with more than one segment dirty. Hence for compound
179 * buffers we need to track which segment the dirty bits correspond to,
238 * the actual size of the dirty bitmap rather than the size of the in
246 * If the map is not be dirty in the transaction, mark
525 bool dirty;
533 * If the bli is dirty and non-aborted, the buffer was clean in the
539 dirty = bip->bli_flags & XFS_BLI_DIRTY;
540 if (dirty && !aborted)
545 * regardless of dirty state. For example, consider an aborted
546 * transaction that invalidated a dirty bli and cleared the dirty
556 * Release the buffer associated with the buf log item. If there is no dirty
585 bool dirty = bip->bli_flags & XFS_BLI_DIRTY;
593 * The bli dirty state should match whether the blf has logged segments
594 * except for ordered buffers, where only the bli should be dirty.
596 ASSERT((!ordered && dirty == xfs_buf_item_dirty_format(bip)) ||
597 (ordered && dirty && !xfs_buf_item_dirty_format(bip)));
632 * We always re-log all the dirty data in a buffer, so usually the
749 "buffer item dirty bitmap (%u uints) too small to reflect %u bytes!",
768 * Mark bytes first through last inclusive as dirty in the buf
852 * Mark bytes first through last inclusive as dirty in the buf
867 * walk each buffer segment and mark them dirty appropriately.