Lines Matching refs:an
25 FS-Cache maintains an in-kernel representation of each object that a netfs is
36 represented by multiple objects - an index may exist in more than one cache -
97 machine. The state for an object is kept in the fscache_object struct, in
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
122 Then when an event is raised (by calling fscache_raise_event()), if the event
165 the cache, it is expected that it will not be possible to look an object
192 Create an object on disk, using the parent as a starting point. This
201 operations the netfs has queued for an object. If creation failed, the
232 And there are terminal states in which an object cleans itself up, deallocates
243 The object comes here if it is dying due to an error, because its parent
274 ready to be deleted. The object processor shouldn't ever see an object in
281 There are a number of events that can be raised to an object state machine:
285 The netfs requested that an object be updated. The state machine will ask
293 (a) when an object's last child object is dropped and
295 (b) when the last operation outstanding on an object is completed.
301 This is signalled when an I/O error occurs during the processing of some
313 This is signalled when the cache backend wants to withdraw an object.