Lines Matching full:an
5 The FS-Cache system provides an API by which actual caches can be supplied to
84 In either case, this may not be an appropriate context in which to access the
148 is backing. An object should retired when put_object() is called if it is
171 An operation can be made exclusive upon an object by setting the
173 an operation needs more processing time, it should be enqueued again.
197 The to_do field is an empty list available for the cache backend to use as
228 This isn't strictly an operation, but should be pointed at a string naming
251 This method is used to look up an object, given that the object is already
278 This method is called to increment the reference count on an object. It
288 These methods are used to exclusively lock an object. It must be possible
297 These methods are used to pin an object into the cache. Once pinned an
302 (*) Check coherency state of an object [mandatory]:
325 All the data stored for this object should be discarded and an
327 with an object update operation.
336 This method is called to indicate that an object has been unbound from its
348 This method is used to discard a reference to an object. The object may
379 highest byte it's willing to store for an object.
381 This method may return -ve if an error occurred or the cache object cannot
389 (*) Reserve cache space for an object's data [optional]:
394 for an object and the metadata used to track it. Zero size should be
401 future expansion. If the amount of space consumed by an object would
403 pages, but not required. An object may be pruned down to its reservation
437 be called at an appropriate point to request CPU time. For instance, the
441 If an I/O error occurs, fscache_io_error() should be called and -ENOBUFS
462 If there was an error such as -ENOMEM, then that should be returned; else
492 This is an multiple page version of the allocate_page() method. pages and
509 If an error occurred, then a negative error code should be returned,
511 in response to an error, such as withdrawing this object.
532 (*) Note occurrence of an I/O error in a cache:
536 This tells FS-Cache that an I/O error occurred in the cache. After this
549 This is called to note the end of an attempt to retrieve a page. The
550 error value should be 0 if successful and an error otherwise.
569 This is called to record the completion of an operation. This deducts
593 (*) Perform coherency check on an object:
599 This asks the netfs to perform a coherency check on an object that has
625 This initialises all the fields in an object representation.
628 (*) Indicate the destruction of an object:
632 This must be called to inform FS-Cache that an object that belonged to a
638 (*) Indicate negative lookup on an object:
642 This is called to indicate to FS-Cache that a lookup process for an object
645 This changes the state of an object to permit reads pending on lookup
649 This may be called multiple times on an object. Only the first call is
653 (*) Indicate an object has been obtained:
657 This is called to indicate to FS-Cache that a lookup process for an object
658 produced a positive result, or that an object was created. This should
661 This changes the state of an object to indicate:
674 This marks an object as having encountered a fatal error (usually EIO)
683 This is called to indicate that the lookup procedure found an object in
688 (*) Indicate that the caching backend killed an object:
693 This is called to indicate that the cache backend preemptively killed an
725 For debugging purposes, this may be used to turn the state that an object