Lines Matching refs:cookie
18 storage, and each level has its own type of cookie object:
23 Cache cookie struct fscache_cache
24 Volume cookie struct fscache_volume
25 Data storage cookie struct fscache_cookie
30 API functions. Each cookie has a debugging ID that is included in trace points
35 and if they ask for one of the same name, they'll get the same cookie. Volume
63 the cache name and that will get it a cache cookie. This is done with::
67 This will look up and potentially create a cache cookie. The cache cookie may
69 that cache cookie will be used. If the cache cookie is not in use by another
78 to reset and discard the cookie.
91 cache cookie and moves the cache to the active state, thereby allowing accesses
109 void fscache_withdraw_cookie(struct fscache_cookie *cookie);
111 on the cookie that each object belongs to. This schedules the specified cookie
130 to clear fields in the cookie and discard the caller's ref on it.
152 * ``cache`` - The parent cache cookie.
175 represented to the network filesystem by a cookie. Cookies are represented in
192 The fields in the cookie that are of interest to the cache backend are:
194 * ``volume`` - The parent volume cookie.
201 cache to be read as the cookie has been created or invalidated.
213 * FSCACHE_COOKIE_RETIRED - The cookie was invalidated when it was
218 * ``inval_counter`` - The number of invalidations done on the cookie.
220 * ``advice`` - Information about how the cookie is to be used.
229 Each cookie has an index key, which may be stored inline to the cookie or
232 void *fscache_get_key(struct fscache_cookie *cookie);
237 Each cookie also has a buffer for coherency data. This may also be inline or
238 detached from the cookie and a pointer is obtained by calling::
240 void *fscache_get_aux(struct fscache_cookie *cookie);
280 * Set up a volume cookie [optional]::
284 This method is called when a volume cookie is being created. The caller
292 * Clean up volume cookie [optional]::
296 This method is called when a volume cookie is being released if
300 * Look up a cookie in the cache [mandatory]::
302 bool (*lookup_cookie)(struct fscache_cookie *cookie);
305 data storage for a cookie. It is called from a worker thread with a
315 struct fscache_cookie *cookie);
320 If successful, ``cookie->cache_priv`` can be set.
323 * Withdraw an object without any cookie access counts held [mandatory]::
325 void (*withdraw_cookie)(struct fscache_cookie *cookie);
327 This method is called to withdraw a cookie from service. It will be
328 called when the cookie is relinquished by the netfs, withdrawn or culled
335 The cookie will have the ``FSCACHE_COOKIE_RETIRED`` flag set on it if the
349 The caller holds a cookie-level access pin to prevent a race with
350 withdrawal and the netfs must have the cookie marked in-use to prevent
356 bool (*invalidate_cookie)(struct fscache_cookie *cookie);
367 void fscache_resume_after_invalidation(struct fscache_cookie *cookie);
369 If the method returns false, caching will be withdrawn for this cookie.
374 void (*prepare_to_write)(struct fscache_cookie *cookie);
390 or resize). The caller holds an access pin on the cookie and must have
391 marked the cookie as in-use.
409 Note that there won't necessarily be anything attached to the cookie's
410 cache_priv yet if the cookie is still being created.
437 * Note cessation of caching on a cookie due to failure::
439 void fscache_caching_failed(struct fscache_cookie *cookie);
441 This notes that a the caching that was being done on a cookie failed in
468 * Get the cookie from a set of cache resources::
472 Pull a pointer to the cookie from the cache resources. This may return a
473 NULL cookie if no cookie was set.