• Home
  • Raw
  • Download

Lines Matching full:will

22 clustered; hashing the object and using the hash as the index will not
53 the range will return the same entry as looking up any other index in
54 the range. Storing to any index will store to all of them. Multi-index
56 into any entry will cause the XArray to forget about the range.
67 using xa_load(). xa_store will overwrite any entry with the
75 xa_cmpxchg(). Like cmpxchg(), it will only succeed if
91 of indices. If you do this, some of the other operations will behave
98 will not need to allocate memory. The xa_reserve() function
99 will store a reserved entry at the indicated index. Users of the
100 normal API will see this entry as containing ``NULL``. If you do
103 in the meantime, xa_release() will do nothing; if instead you
105 Using xa_insert() on a reserved entry will fail.
108 will return ``true``.
129 Setting or clearing a mark on any index of a multi-index entry will
131 index will return the same result.
152 Using xa_store(), xa_cmpxchg() or xa_insert() will
154 ``NULL`` will mark the entry as being in use, like xa_reserve().
175 and the GFP flags specified will be ignored.
239 object you have found before calling xa_unlock(). This will
297 the xa_lock; the xa_lock is used for lockdep validation and will be used
303 in this case, as it will save you from walking the tree twice.
338 will attempt to allocate more memory using the specified gfp flags and
343 can try harder to allocate more memory. It will return ``true`` if it
347 ``ENOMEM``), then it will free the memory previously allocated.
388 will be handled by xas_retry().
394 to store every entry in a range. It will set ENOMEM in the xa_state if
401 xas_store() will not reset the marks on that entry; if you want
404 The xas_load() will walk the xa_state as close to the entry
411 will generally make the next operation walk the cursor to the desired
419 if the cursor has been walked to an entry, then it will find the next
420 entry after the one currently referenced. If not, it will return the
422 move to the next present entry instead of xas_find() will save
427 not been walked, it will return the entry at the index of the xa_state,
428 if it is marked. Otherwise, it will return the first marked entry after
443 XArray; they will do nothing if you have called xas_pause() or xas_set()
456 any index will change the value of the entry retrieved from any index.
457 Setting or clearing a mark on any index will set or clear the mark
462 together will save over 4kB.
466 Calling xas_load() with a multi-index xa_state will walk the
470 will return the first entry within the range or ``NULL`` if there are no
471 entries in the range. The xas_for_each_conflict() iterator will
475 in the xa_state will not be changed. When iterating over an XArray
477 of a multi-index entry, it will not be altered. Subsequent calls
478 or iterations will move the index to the first index in the range.
479 Each entry will only be returned once, no matter how many indices it
483 supported. Using either of these functions on a multi-index entry will
486 Storing ``NULL`` into any index of a multi-index entry will set the