Lines Matching full:state

13  (*) Object management state machine.
93 Object Management State Machine
96 Within FS-Cache, each active object is managed by its own individual state
97 machine.  The state for an object is kept in the fscache_object struct, in
98 object->state.  A cookie may point to a set of objects that are in different
101 Each state has an action associated with it that is invoked when the machine
102 wakes up in that state.  There are four logical sets of states:
112      and that update the state of objects.
120 When a state has finished processing, it will usually set the mask of events in
135      particular work item.  These state actions may be doing sequences of
148 state machine at once, this simplifies the locking, particularly with respect
157 The object state machine has a set of states that it can be in.  There are
159 object to transit to a state that allows access to its children:
161  (1) State FSCACHE_OBJECT_INIT.
171  (2) State FSCACHE_OBJECT_LOOKING_UP.
189  (3) State FSCACHE_OBJECT_CREATING.
193      coherency data indicated what's on disk is out of date.  In this state,
207  (4) State FSCACHE_OBJECT_AVAILABLE.
209      A transient state in which pending operations are started, child objects
210      are permitted to advance from FSCACHE_OBJECT_INIT state, and temporary
213  (5) State FSCACHE_OBJECT_ACTIVE.
215      The normal running state.  In this state, requests the netfs makes will be
218  (6) State FSCACHE_OBJECT_INVALIDATING.
220      The object is undergoing invalidation.  When the state comes here, it
223      continue to the FSCACHE_OBJECT_UPDATING state.
225  (7) State FSCACHE_OBJECT_UPDATING.
227      The state machine comes here to update the object in the cache from the
234  (8) State FSCACHE_OBJECT_LC_DYING.
240  (9) State FSCACHE_OBJECT_DYING.
248      before advancing to the next state.
250 (10) State FSCACHE_OBJECT_ABORT_INIT.
252      The object comes to this state if it was waiting on its parent in
254      so that the parent may proceed from the FSCACHE_OBJECT_DYING state.
256 (11) State FSCACHE_OBJECT_RELEASING.
257 (12) State FSCACHE_OBJECT_RECYCLING.
261      cookie.  In the first state, the cached data is expected to persist, and
264 (13) State FSCACHE_OBJECT_WITHDRAWING.
266      The object transits to this state if the cache decides it wants to
270 (14) State FSCACHE_OBJECT_DEAD.
272      The object transits to this state when the in-memory object record is
274      this state.
280 There are a number of events that can be raised to an object state machine:
283      The netfs requested that an object be updated.  The state machine will ask
294      This is used to proceed from the dying state.
311 state machine, it doesn't matter if there's a collision with both ends trying
312 to sever the connection at the same time.  The state machine can just pick