Lines Matching full:backend

4 Cache Backend API
34 The cache backend and the network filesystem can both ask for cache cookies -
52 There are a few fields that the cache backend might be interested in.  The
62 When a cache backend wants to bring a cache online, it should first register
73 If successful, the cache backend can then start setting up the cache.  In the
74 event that the initialisation fails, the cache backend should call::
98 The cache backend can withdraw a cache from service by calling this function::
112 for withdrawal.  This gets offloaded to a workqueue.  The cache backend can
117 Once all the cookies are withdrawn, a cache backend can withdraw all the
150 There are a number of fields here that are of interest to the caching backend:
192 The fields in the cookie that are of interest to the cache backend are:
210       * FSCACHE_COOKIE_HAVE_DATA - The backend should set this if it
268 The cache backend implements the cache management API by providing a table of
277 This contains a printable name for the cache backend driver plus a number of
318      stuff whilst the cache backend gets on with the job of creating things.
329      by the cache backend or closed after a period of non-use by fscache.
344      This method is called to inform the cache backend of a change in size of
345      the netfs file due to local truncation.  The cache backend should make all
360      that the cache backend should throw away all the data in the cache for
365      to accept I/O again, the backend should release the block by calling::
393      If it can, the backend should attach any resources it needs to keep around
416 A cache backend provides a data I/O API by through the netfs library's ``struct
426 FS-Cache provides some utilities that a cache backend may make use of: