Lines Matching refs:it

6 FS-Cache for it to then serve out to network filesystems and other interested
50      successful and will release it upon withdrawal of the cache.
57 This function may return -ENOMEM if it ran out of memory or -EEXIST if the tag
101 and is for use by the cache as it sees fit.
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
148      is backing.  An object should retired when put_object() is called if it is
165      FS-Cache has a pool of threads that it uses to give CPU time to the
169      rid of it when its usage count reaches 0.
172      appropriate flag before enqueuing it with fscache_enqueue_operation().  If
173      an operation needs more processing time, it should be enqueued again.
187      backend to do the operation.  The backend may get extra refs to it by
194      submit it to the thread pool.  CacheFiles, for example, uses this to queue
195      page examination when it detects PG_lock being cleared.
198      it sees fit.
239      the object to initialise it prior to returning.
242      multiple lookup calls to turn it into a more convenient form.  FS-Cache
253      in the cache if it can.
256      possible if it determines the object doesn't exist in the cache.  If the
257      object is found to exist and the netfs indicates that it is valid then
259      position to have data stored in it.  Similarly, fscache_obtained_object()
270      This method is called to ask the cache to release any resources it was
338      retire it if it's in state FSCACHE_OBJECT_RECYCLING.
349      be freed when all the references to it are released.
379      highest byte it's willing to store for an object.
394      for an object and the metadata used to track it.  Zero size should be
402      exceed the reservation, it's permitted to refuse requests to allocate
415      as it can before calling, but most of the work belongs to the backend.
418      backend managed to reserve a backing block; -ENOBUFS or -ENOMEM if it
456      This is like the read_or_alloc_page() method, except it is handed a list
475      This is like the read_or_alloc_page() method, except that it shouldn't
522      cache backend should tear down any internal representation or tracking it
579      This sets the limit FS-Cache imposes on the highest byte it's willing to
634      of the cache withdrawal process when it is stopped pending destruction of
646      completion to go off and start fetching data from the netfs server as it's
665 	    now go and look for it; and
675      and causes it to move into a state whereby it will be withdrawn as soon