Lines Matching refs:that

94 However, since it's unlikely that any two netfs's are going to want to define
183 parent for the non-index object will be queried. Any indices above that
185 need to be supplied for any non-index object or any index that will only
189 cache in the parent's list will be chosen, or failing that, the first
194 This function will be called with the netfs data that was passed to the
195 cookie acquisition function and the maximum length of key data that it may
201 This function will be called with the netfs data that was passed to the
210 This function will be called with the netfs data that was passed to the
211 cookie acquisition function and the maximum length of auxiliary data that
223 This function will be called to check that a match found in the cache for
228 If this function is absent, it will be assumed that matching objects in a
249 If the context is not used or is a type of object that won't go out of
256 This is called by the cache to indicate that it is retaining in-memory
257 information for this page and that the netfs should uncache the page when
259 or not. Note that several pages at once may be presented for marking.
268 This is called by FS-Cache to indicate that a backing store is being
269 unbound from a cookie and that all the marks on the pages should be
270 cleared to prevent confusion. Note that the cache will have torn down all
271 its tracking information so that the pages don't need to be explicitly
308 FS-Cache as to which cache should be used. The problem with doing that is that
309 FS-Cache will always pick the first cache that was registered.
331 The third step is to inform FS-Cache about part of an index hierarchy that can
344 Note that this function never returns an error - all errors are handled
350 Note also that no indices are actually created in a cache until a non-index
369 index and an inode would be allocated that acts as a volume type and hash chain
378 that index, creating another index for vnodes (AFS inode equivalents):
391 identical to index cookie acquisition. The only difference is that the type in
406 difference is that the type in the object definition should be something other
433 Note that attempts to read or write data pages in the cache over this size may
446 three functions that are used to do this.
478 The cookie argument must specify a cookie for an object that isn't an index,
489 (1) The mark_pages_cached() cookie operation will be called on that page.
505 (*) An argument that's 0 on success or negative for an error code.
507 If an error occurs, it should be assumed that the page contains no usable
517 (1) The mark_pages_cached() cookie operation will be called on that page.
538 This is similar to the fscache_read_or_alloc_page() function, except that it
580 anyone waiting for that bit will be woken up.
612 (3) If there was an general error, then that error will be returned.
627 Note that a return of -ENODATA, -ENOBUFS or any other error does not preclude
645 and any that have PG_fscache set will be uncached.
662 Note that pages can't be explicitly deleted from the a data file. The whole
665 Furthermore, note that this does not cancel the asynchronous read or write
703 attached to an inode. This assumes that the pages on the inode correspond on a
709 This takes the netfs cookie that the pages were cached with and the inode that
738 Note that partial updates may happen automatically at other times, such as when
787 There are a number of operations that can be used to control cookies:
817 Note that this doesn't pin an object in a cache; it can still be culled to
832 Not only that but all child objects will also be retired.
855 Sometimes it will be necessary to invalidate an object that contains data.
860 To indicate that a cache object should be invalidated, the following function
869 that, operations will be queued again behind the invalidation operation.
888 PG_fscache is used to indicate that the page is known by the cache, and that
890 to the netfs that the cache has an interest in this page, where an interest may
903 This bit does not overlap with such as PG_private. This means that FS-Cache
904 can be used with a filesystem that uses the block buffering code.