Lines Matching refs:xa_state
317 The advanced API is based around the xa_state. This is an opaque data
319 This macro initialises the xa_state ready to start walking around the
322 from the top every time. The contents of the xa_state are protected by
328 The xa_state is also used to store errors. You can call
330 the xa_state is in an error state before proceeding, so there's no need
337 If the xa_state is holding an ``ENOMEM`` error, calling xas_nomem()
339 cache it in the xa_state for the next attempt. The idea is that you take
366 - An XArray node. May be visible when using a multi-index xa_state.
394 to store every entry in a range. It will set ENOMEM in the xa_state if
404 The xas_load() will walk the xa_state as close to the entry
405 as it can. If you know the xa_state has already been walked to the
421 entry at the index of the xa_state. Using xas_next_entry() to
426 The xas_find_marked() function is similar. If the xa_state has
427 not been walked, it will return the entry at the index of the xa_state,
429 the entry referenced by the xa_state. The xas_next_marked()
435 After you have done the necessary work and wish to resume, the xa_state
442 the xa_state cursor to have been moved to the appropriate location in the
466 Calling xas_load() with a multi-index xa_state will walk the
467 xa_state to the right location in the tree, but the return value is not
475 in the xa_state will not be changed. When iterating over an XArray
482 Using xas_next() or xas_prev() with a multi-index xa_state is not