Lines Matching refs:called

70 In CacheFS's case, this is called by put_super().
99 A sysfs directory called /sys/fs/fscache/<cachetag>/ is created if CONFIG_SYSFS
148      is backing.  An object should retired when put_object() is called if it is
168      method is called to give the op CPU time, and the release method to get
193      appropriately by the backend and fscache_enqueue_retrieval() called to
238      cookie in a particular cache.  fscache_object_init() should be called on
258      fscache_obtained_object() should be called once the object is in a
260      should also be called once a non-present object has been created.
262      If a lookup error occurs, fscache_object_lookup_error() should be called
270      This method is called to ask the cache to release any resources it was
278      This method is called to increment the reference count on an object.  It
306      This method is called to have the cache check the saved auxiliary data of
315      This is called to update the index entry for the specified object.  The
324      This is called to invalidate a data object (as pointed to by op->object).
329      fscache_op_complete() must be called on op before returning.
336      This method is called to indicate that an object has been unbound from its
356      This is called to ask the backend to synchronise a cache with its backing
364      This is called to ask a cache to perform any page dissociations as part of
372      This is called to indicate to the cache that certain attributes on a netfs
393      This is called to request that cache space be reserved to hold the data
413      This is called to attempt to read a netfs page from the cache, or to
423      called.
425      The fscache_mark_pages_cached() should be called for the page if any cache
437      be called at an appropriate point to request CPU time.  For instance, the
441      If an I/O error occurs, fscache_io_error() should be called and -ENOBUFS
442      returned if possible or fscache_end_io() called with a suitable error
445      fscache_put_retrieval() should be called after a page or pages are dealt
501      This is called to write from a page on which there was a previously
505      This method is called asynchronously from the FS-Cache thread pool.  It is
521      This is called when a netfs page is being evicted from the pagecache.  The
537      has been called, only resource dissociation operations (object and page
549      This is called to note the end of an attempt to retrieve a page.  The
559      This is called to record the fact that one or more pages have been dealt
569      This is called to record the completion of an operation.  This deducts
589      This marks a set of pages as being cached.  After this has been called,
632      This must be called to inform FS-Cache that an object that belonged to a
642      This is called to indicate to FS-Cache that a lookup process for an object
649      This may be called multiple times on an object.  Only the first call is
657      This is called to indicate to FS-Cache that a lookup process for an object
659      only be called once for any particular object.
683      This is called to indicate that the lookup procedure found an object in
693      This is called to indicate that the cache backend preemptively killed an
717      op->op.processor callback function.  This function may be called from