Lines Matching full:should
21 The cache definition (struct fscache_cache) should be initialised by calling::
39 The cache should then be registered with FS-Cache by passing a pointer to the
46 Two extra arguments should also be supplied:
48 * "fsdef" which should point to the object representation for the FS-Cache
53 * "tagname" which, if given, should be a text string naming this cache. If
135 Structures of this type should be allocated by the cache backend and
141 that refer to a particular object. In such a case it should be printed
145 is backing. An object should retired when put_object() is called if it is
146 in state FSCACHE_OBJECT_RECYCLING. The fscache_object struct should be
170 an operation needs more processing time, it should be enqueued again.
189 do this, the retrieval->op.processor method pointer should be set
226 This isn't strictly an operation, but should be pointed at a string naming
236 cookie in a particular cache. fscache_object_init() should be called on
250 allocated and attached to the cookie. This should instantiate that object
253 The method should call fscache_object_lookup_negative() as soon as
256 fscache_obtained_object() should be called once the object is in a
258 should also be called once a non-present object has been created.
260 If a lookup error occurs, fscache_object_lookup_error() should be called
278 It should return the object pointer if successful.
305 the object against the netfs's idea of the state. 0 should be returned
314 new information should be in object->cookie->netfs_data. This can be
323 All the data stored for this object should be discarded and an
324 attr_changed operation should be performed. The caller will follow up
335 cookie, and that the cache should release the object's resources and
338 This method should not attempt to release any references held by the
376 It should also call fscache_set_store_limit() to indicate to FS-Cache the
392 for an object and the metadata used to track it. Zero size should be
395 This should return 0 if successful, -ENOSPC if there isn't enough space
415 If there's no page in the cache, then -ENODATA should be returned if the
419 If there is suitable data in the cache, then a read operation should be
420 queued and 0 returned. When the read finishes, fscache_end_io() should be
423 The fscache_mark_pages_cached() should be called for the page if any cache
428 The retrieval record pointed to by op should be retained for each page
433 pool. If this is desired, the op->op.processor should be set to point to
434 the appropriate processing routine, and fscache_enqueue_retrieval() should
439 If an I/O error occurs, fscache_io_error() should be called and -ENOBUFS
443 fscache_put_retrieval() should be called after a page or pages are dealt
460 If there was an error such as -ENOMEM, then that should be returned; else
461 if one or more pages couldn't be read or allocated, then -ENOBUFS should
463 should be returned. If all the pages are dispatched then 0 should be
475 It should, however, set up any internal metadata required such that
478 If there's no backing block available, then -ENOBUFS should be returned
480 allocated, then the netfs page should be marked and 0 returned.
491 nr_pages should be treated as for the read_or_alloc_pages() method.
507 If an error occurred, then a negative error code should be returned,
508 otherwise zero should be returned. FS-Cache will take appropriate action
520 cache backend should tear down any internal representation or tracking it
547 error value should be 0 if successful and an error otherwise.
598 netfs to use. data and datalen should specify where the auxiliary data
611 The coherency data indicates that the object is obsolete and should
652 produced a positive result, or that an object was created. This should
688 object. The why parameter should be set to indicate the reason: