Lines Matching full:cursor

492 builder maintains a publicly visible cursor that tracks the progress of the
496 cursor position within the record ID space.
2280 4. Pass the xfbtree object to the btree cursor creation function for the
2285 5. Pass the btree cursor to the regular btree functions to make queries against
2287    For example, a btree cursor for an rmap xfbtree can be passed to the
2288    ``xfs_rmap_*`` functions just like any other btree cursor.
2292 6. When finished, delete the btree cursor, destroy the xfbtree object, free the
3196 Naturally, a scan through a keyspace requires a scan cursor object to track the
3198 Because this keyspace is sparse, this cursor contains two parts.
3199 The first part of this scan cursor object tracks the inode that will be
3200 examined next; call this the examination cursor.
3201 Somewhat less obviously, the scan cursor object must also track which parts of
3204 Call this the visited inode cursor.
3206 Advancing the scan cursor is a multi-step process encapsulated in
3210    inode cursor.
3212    advancing the cursor.
3219    a. Move the examination cursor to the point of the inumber keyspace that
3222    b. Adjust the visited inode cursor to indicate that it has "visited" the
3224       XFS inumbers are segmented, so the cursor needs to be marked as having
3237    a. Move the examination cursor ahead to the next inode marked as allocated
3240    b. Adjust the visited inode cursor to point to the inode just prior to where
3241       the examination cursor is now.
3243       created in the part of the inode keyspace that the visited inode cursor
3246 5. Get the incore inode for the inumber of the examination cursor.
3248    it was safe to advance the examination cursor across the entire keyspace,
3258 2. Advance the scan cursor (``xchk_iscan_iter``) to get the next inode.
3265    c. While still holding the inode lock, adjust the visited inode cursor
3719 with the live update hooks is that the scan cursor tracks which *parent*
3739 A second coordinated inode scan cursor is used for comparisons.
3795    a. Create a btree cursor for the in-memory btree.
3806    a. Create a btree cursor for the in-memory btree.
4168       This advances the cursor.
4729       3. Position one slab cursor at the start of the inode's records in the
4734       4. Position a second slab cursor at the start of the per-file tuple slab.
4738          cursor:
4740          a. If the per-AG cursor is at a lower point in the keyspace than the
4741             per-file cursor, then the per-AG cursor points to a missing parent
4744             cursor.
4746          b. If the per-file cursor is at a lower point in the keyspace than
4747             the per-AG cursor, then the per-file cursor points to a dangling
4750             cursor.