Lines Matching refs:that

31  (*) "ops" is a pointer to the table of operations that the backend supports on
79  (1) that of the userspace process that issued the netfs operation that caused
82  (2) that of one of the processes in the FS-Cache thread pool.
117      The fields that might be of use to the backend describe the object
143      The debug_id is a simple integer that can be used in debugging messages
144      that refer to a particular object.  In such a case it should be printed
147      Each object contains a pointer to the cookie that represents the object it
165      FS-Cache has a pool of threads that it uses to give CPU time to the
166      various asynchronous operations that need to be done as part of driving
219 The cache backend provides FS-Cache with a table of operations that can be
251      This method is used to look up an object, given that the object is already
252      allocated and attached to the cookie.  This should instantiate that object
257      object is found to exist and the netfs indicates that it is valid then
263      to abort the lookup of that object.
336      This method is called to indicate that an object has been unbound from its
337      cookie, and that the cache should release the object's resources and
368  (*) Notification that the attributes on a netfs file changed [mandatory]:
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
404      size if larger than that already.
426      metadata is retained.  This will indicate to the netfs that the page needs
462      If there was an error such as -ENOMEM, then that should be returned; else
475      This is like the read_or_alloc_page() method, except that it shouldn't
476      read from the cache, even if there's data there that could be retrieved.
477      It should, however, set up any internal metadata required such that
503      pages that don't have mappings.
530 FS-Cache provides some utilities that a cache backend may make use of:
536      This tells FS-Cache that an I/O error occurred in the cache.  After this
553  (*) Record that one or more pages being retrieved or allocated have been dealt
559      This is called to record the fact that one or more pages have been dealt
599      This asks the netfs to perform a coherency check on an object that has
617 	    The coherency data indicates that the object is obsolete and should
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
647      known at this point that there can't be any data in the cache.
657      This is called to indicate to FS-Cache that a lookup process for an object
658      produced a positive result, or that an object was created.  This should
664 	    this object, that there may be data available, and that reads can
667         (2) that writes may now proceed against this object.
670  (*) Indicate that object lookup failed:
702      For debugging purposes, this may be used to turn the state that an object