Lines Matching refs:xa_state

302 The advanced API is based around the xa_state.  This is an opaque data
304 macro.  This macro initialises the xa_state ready to start walking
309 The xa_state is also used to store errors.  You can call
311 the xa_state is in an error state before proceeding, so there's no need
318 If the xa_state is holding an ``ENOMEM`` error, calling xas_nomem()
320 cache it in the xa_state for the next attempt.  The idea is that you take
347      - An XArray node.  May be visible when using a multi-index xa_state.
375 to store every entry in a range.  It will set ENOMEM in the xa_state if
385 The xas_load() will walk the xa_state as close to the entry
386 as it can.  If you know the xa_state has already been walked to the
402 entry at the index of the xa_state.  Using xas_next_entry() to
407 The xas_find_marked() function is similar.  If the xa_state has
408 not been walked, it will return the entry at the index of the xa_state,
410 the entry referenced by the xa_state.  The xas_next_marked()
416 After you have done the necessary work and wish to resume, the xa_state
423 xas_clear_mark() functions require the xa_state cursor to have
448 Calling xas_load() with a multi-index xa_state will walk the
449 xa_state to the right location in the tree, but the return value is not
457 in the xa_state will not be changed.  When iterating over an XArray
464 Using xas_next() or xas_prev() with a multi-index xa_state