Lines Matching +full:start +full:- +full:up
1 .. SPDX-License-Identifier: GPL-2.0
9 - Overview.
10 - Buffered read helpers.
11 - Read helper functions.
12 - Read helper structures.
13 - Read helper operations.
14 - Read helper procedure.
15 - Read helper cache API.
34 The library provides a set of read helpers that handle the ->readpage(),
35 ->readahead() and much of the ->write_begin() VM operations and translate them
44 * Allows the netfs to arbitrarily split reads up into pieces, even ones that
52 * Handles local caching, allowing cached data and server-read data to be
69 ---------------------
103 For ->readahead() and ->readpage(), the network filesystem should just jump
104 into the corresponding read helper; whereas for ->write_begin(), it may be a
113 If an error occurs and netfs_priv is non-NULL, ops->cleanup() will be called to
125 the operation was asynchronous (ie. whether the follow-on processing can be
130 ----------------------
140 loff_t start;
154 may or may not point to inode->i_data.
163 to the helper functions or set during the request. The ->cleanup() op will
164 be called if this is non-NULL at the end.
166 * ``start``
169 The file position of the start of the read request and the length. These
170 may be altered by the ->expand_readahead() op.
174 The size of the file at the start of the request.
192 loff_t start;
207 * ``start``
210 The file position of the start of this slice of the read request and the
216 network filesystem or cache should start the operation this far into the
242 ----------------------
266 the file for reference and can modify the ->netfs_priv value.
280 The cache gets to store its state in ->cache_resources and must set a table
295 Expansion is communicated by changing ->start and ->len in the request
296 structure. Note that if any change is made, ->len must be increased by at
297 least as much as ->start is reduced.
302 subrequest. The filesystem can use this, for example, to chop up a request
311 reading. In the subrequest, ->start, ->len and ->transferred indicate what
317 uptodate, unlocking them or dropping their refs - the helpers need to deal
336 It should return 0 if everything is now fine, -EAGAIN if the page should be
347 filesystem can clean up ->netfs_priv.
352 ---------------------
356 * Set up the request.
408 * The request structures will be cleaned up when everything has completed.
412 ---------------------
418 The network filesystem's ->begin_cache_operation() method is called to set up a
472 [Required] Called to clean up the resources at the end of the read request.
480 The function is passed poiners to the start and length in its parameters,
481 plus the size of the file for reference, and adjusts the start and length
490 downloaded from the server or read from the cache - or whether slicing
491 should be given up at the current point.
495 [Required] Called to configure the next slice of a request. ->start and
496 ->len in the subrequest indicate where and how big the next slice can be;
501 [Required] Called to read from the cache. The start file offset is given
503 given a hint requesting that it seek forward from that start position for
514 [Required] Called to write to the cache. The start file offset is given