Lines Matching refs:it

37 or even by no objects (it may not be cached).
89 those cookies are hidden from it.
101 Each state has an action associated with it that is invoked when the machine
105      representations are hierarchical, and it is expected that an object must
120 When a state has finished processing, it will usually set the mask of events in
121 which it is interested (object->event_mask) and relinquish the worker thread.
158 The object state machine has a set of states that it can be in.  There are
165      the cache, it is expected that it will not be possible to look an object
176      object is represented there, and if it is, to see if it's valid (coherency
221      The object is undergoing invalidation.  When the state comes here, it
222      discards all pending read, write and attribute change operations as it is
223      going to clear out the cache entirely and reinitialise it.  It will then
237      The object comes here if it is dying because of a lookup or creation
243      The object comes here if it is dying due to an error, because its parent
253      The object comes to this state if it was waiting on its parent in
260      The object comes to one of these two states when dying once it is rid of
261      all its children, if it is dying because the netfs relinquished its
263      in the second it will be deleted.
267      The object transits to this state if the cache decides it wants to
307      These are signalled when the netfs relinquishes a cookie it was using.
318 state machine, it doesn't matter if there's a collision with both ends trying
320 which one it wants to honour, and that effects the other.