Lines Matching full:be

32 	 (4) Declaring a cookie to be in use
52 or server address, volume ID or share name).  This must be rendered as a
53 printable string that can be used as a directory name (ie. no '/' characters
61 object key.  Object keys are binary blobs and only need to be unique within
84 structures being used.  The actual operation can then be issued and conflicting
85 invalidations can be detected upon completion.
106 The volume key must be a printable string with no '/' characters in it.  It
107 should begin with the name of the filesystem and should be no longer than 254
108 characters.  It should uniquely represent the volume and will be matched with
116 The specified coherency data is stored in the cookie and will be matched
117 against coherency data stored on disk.  The data pointer may be NULL if no data
119 be invalidated.
135 This will cause the volume to be committed or removed, and if sealed the
136 coherency data will be set to the value supplied.  The amount of coherency data
138 data cookies obtained in this volume must be relinquished before the volume is
158 key is a binary blob of the given length and must be unique for the volume.
164 of size aux_data_len will be allocated and the coherency data copied in.  It is
167 coherency data can be updated.
169 The file size of the object being cached should also be provided.  This may be
170 used to trim the data and will be stored with the coherency data.
205 so may not be complete by the time the function returns.
211 resources will be released to reduce system resource consumption.
213 A cookie must be marked in-use before it can be accessed for read, write or
214 resize - and an in-use mark must be kept whilst there is dirty data in the
219 in-use, it must be unused.
226 should be called to notify the cache::
233 be called from ``->setattr()`` inode operation under the inode lock.
259 nothing), then one of the other two functions can be issued.
267 partially populated region (a hole) in the disk content.  This may be to ignore
270 The read and write functions can be given an optional termination function that
271 will be run on completion::
277 If a termination function is given, the operation will be run asynchronously
278 and the termination function will be called upon completion.  If not given, the
279 operation will be run synchronously.  Note that in the asynchronous case, it is
293 following should be called::
305 Sometimes it will be necessary to invalidate an object that contains data.
306 Typically this will be necessary when the server informs the network filesystem
311 To indicate that a cache object should be invalidated, the following should be
332 resources required need to be pinned at the point the modification is made (for
339    in-use is held on the cookie for this inode.  It can only be changed if the
357 The *set* function is intended to be called from the filesystem's
362 The *unpin* function is intended to be called from the filesystem's
366 The *clear* function is intended to be called from the netfs's ``evict_inode``
367 superblock operation.  It must be called *after*
370 be updated.
378 if the mark is already present, it needs to wait for it to be removed first
387 If caching is to be attempted, pages should be waited for and then marked using
404 And if an error occurs before that point is reached, the marks can be removed
413 going to be written (it doesn't have to align to page boundaries necessarily,
415 caching parameter indicates if caching should be skipped, and if false, the
419 the cache object to be written to, i_size indicates the size of the netfs file
421 term_func_priv will be passed, along with the error or amount written.
435 To inform fscache that a page might now be in the cache, the following function
436 should be called from the ``release_folio`` address space op::