Lines Matching refs:cache
67 entire in-cache hierarchy for this netfs will be scrapped and begun
106 cache. Any such objects created within an index will be created in the
107 first cache only. The cache in which an index is created can be
108 controlled by cache tags (see below).
179 (3) A function to select the cache in which to store an index [optional].
181 This function is invoked when an index needs to be instantiated in a cache
189 cache in the parent's list will be chosen, or failing that, the first
190 cache in the master list.
203 this is a data file. The size may be used to govern how much cache must
204 be reserved for this file in the cache.
223 This function will be called to check that a match found in the cache for
226 whether the index entry in a cache is still valid.
229 cache are always valid.
238 the cache and copy it into the netfs's structures.
243 The cache read/write functions are passed a context which is then passed
254 (9) A function to mark a page as retaining cache metadata [optional].
256 This is called by the cache to indicate that it is retaining in-memory
266 (10) A function to unmark all the pages retaining cache metadata [mandatory].
270 cleared to prevent confusion. Note that the cache will have torn down all
281 The first step is to declare the network filesystem to the cache. This also
305 FS-Cache permits the use of more than one cache. To permit particular index
306 subtrees to be bound to particular caches, the second step is to look up cache
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.
350 Note also that no indices are actually created in a cache until a non-index
363 cell->cache =
372 vlocation->cache =
373 fscache_acquire_cookie(cell->cache,
380 volume->cache =
381 fscache_acquire_cookie(vlocation->cache,
390 The fourth step is to request a data file be created in the cache. This is
394 vnode->cache =
395 fscache_acquire_cookie(volume->cache,
405 the cache. This is almost identical to index cookie acquisition. The only
410 xattr->cache =
411 fscache_acquire_cookie(vnode->cache,
424 This doesn't automatically reserve any space in the cache, but permits the
425 cache to adjust its metadata for data tracking appropriately:
429 The cache will return -ENOBUFS if there is no backing cache or if there is no
430 space to allocate any extra metadata required in the cache. The attributes
433 Note that attempts to read or write data pages in the cache over this size may
445 And the sixth step is to store and retrieve pages in the cache. There are
455 (3) A page should only be written to the cache if previous read or allocated.
457 This permits the cache to maintain its page tracking in proper order.
487 Else if there's a copy of the page resident in the cache:
491 (2) The function will submit a request to read the data from the cache's
514 Otherwise, if there's not a copy available in cache, but the cache may be able
519 (2) A block may be reserved in the cache and attached to the object at the
525 read any data from the cache.
531 Alternatively, if there's not expected to be any data in the cache for a page
539 never reads from the cache. It will return 0 if a block has been allocated,
541 before writing to the cache.
552 written back to the cache:
570 Else if space can be allocated in the cache to hold this page:
574 (2) The function will submit a request to write the data to cache's backing
582 Else if there's no space available in the cache, -ENOBUFS will be returned. It
636 read from the cache and also not read from the underlying filesystem then
657 This function permits the cache to release any in-memory representation it
660 make sure the cache's in-memory tracking information gets torn down.
672 to see if a page is being written to the cache, and:
682 conflict with the cache trying to write pages to the cache (which may itself
696 in which case the page will not be stored in the cache this time.
704 1:1 basis with the pages in the cache.
711 written to the cache and for the cache to finish with the page generally. No
720 cache, the following function can be called:
794 These operations permit data cookies to be pinned into the cache and to
798 isn't backed by a cache, -EOPNOTSUPP if the cache doesn't support pinning,
806 This permits a netfs to request cache space be reserved to store up to the
813 backed by a cache, -EOPNOTSUPP if the cache doesn't support reservations,
817 Note that this doesn't pin an object in a cache; it can still be culled to
860 To indicate that a cache object should be invalidated, the following function
868 cache has had a chance to insert a barrier in the operations queue. After
888 PG_fscache is used to indicate that the page is known by the cache, and that
889 the cache must be informed if the page is going to go away. It's an indication
890 to the netfs that the cache has an interest in this page, where an interest may