Lines Matching refs:it
14 may or may not have anything associated with it, but the netfs doesn't
91 (2) To make it easier to discard a subset of all the files cached based around
94 However, since it's unlikely that any two netfs's are going to want to define
96 restraints as possible on how an index is structured and where it is placed in
98 it's not recommended.
110 (2) The entry data must be atomically journallable, so it is limited to about
188 If this function is not supplied or if it returns NULL then the first
195 cookie acquisition function and the maximum length of key data that it may
197 return the quantity it wrote.
212 it may provide. It should write the auxiliary data into the given buffer
213 and return the quantity it wrote.
224 this object is valid. For instance with AFS it could check the auxiliary
228 If this function is absent, it will be assumed that matching objects in a
238 the cache and copy it into the netfs's structures.
247 reference to it.
256 This is called by the cache to indicate that it is retaining in-memory
258 it has finished. This does not indicate whether there's data on the disk
307 representation tags. This step is optional; it can be left entirely up to
316 will never return an error. It may return a dummy tag, however, if it runs out
319 Any representation so obtained must be released by passing it to this function:
323 The tag will be retrieved by FS-Cache when it calls the object definition
353 This is all handled transparently, and the netfs doesn't see any of it.
356 must be enabled to do anything with it. A disabled cookie can be enabled by
368 Then when a volume location was accessed, it would be entered into the cell's
407 than index type. Whilst the parent object could be an index, it's more likely
408 it would be some other type of object such as a data file.
437 some point in the future, and as such, it may happen after the function returns
450 (1) A page should not be re-read or re-allocated without uncaching it first.
479 the page specified will have the data loaded into it (and is also used to
507 If an error occurs, it should be assumed that the page contains no usable
511 an error, but it might be called in interrupt context if the read is
524 This function may also return -ENOMEM or -EINTR, in which case it won't have
538 This is similar to the fscache_read_or_alloc_page() function, except that it
605 (1) Any page it can retrieve data for is removed from pages and nr_pages and
624 complete. It will be called in process context if error != 0, but it may
657 This function permits the cache to release any in-memory representation it
677 to wait for it to finish if it is.
691 some reason and if it returns true, the page has been uncached and can now be
695 storage request to complete, or it may attempt to cancel the storage request -
725 with a cookie is correct. It returns 0 if it is and -ESTALE if it isn't; it
747 disabled, it ignores all attempts to acquire child cookies; check, update or
748 invalidate its state; allocate, read or write backing pages - though it is
817 Note that this doesn't pin an object in a cache; it can still be culled to
818 make space if it's not in use.
831 copies of it will be removed from all active caches in which it is present.
855 Sometimes it will be necessary to invalidate an object that contains data.
857 change - at which point the netfs has to throw away all the state it had for an
865 This can be called with spinlocks held as it defers the work to a thread pool.
872 auxiliary data update operation as it is very likely these will have changed.
875 to have reached a point at which it can start submitting ordinary operations
891 be a pointer to it, resources allocated or reserved for it, or I/O in progress
892 upon it.
895 determine whether it needs to uncache a page or update it.
898 will be called on a page to get rid of it, even if PG_private is not set. This
900 after fscache_read_or_alloc_pages() as the former will try and release pages it