Lines Matching full:read
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.
23 just includes turning various VM buffered read operations into requests to read
31 Buffered Read Helpers
34 The library provides a set of read helpers that handle the ->readpage(),
50 * Allows the netfs to partially fulfil a read, which will then be resubmitted.
52 * Handles local caching, allowing cached data and server-read data to be
64 includes a mandatory method to issue a read operation along with a number of
68 Read Helper Functions
71 Three read helpers are provided::
91 for the use of the read helpers:
101 Both of these values will be stored into the read request structure.
104 into the corresponding read helper; whereas for ->write_begin(), it may be a
109 The helpers manage the read request, calling back into the network filesystem
115 occurs, the request will get partially completed if sufficient data is read.
123 which should be called to complete a read subrequest. This is given the number
129 Read Helper Structures
132 The read helpers make use of a couple of structures to maintain the state of
133 the read. The first is a structure that manages a read request as a whole::
153 The inode and the address space of the file being read from. The mapping
169 The file position of the start of the read request and the length. These
187 The second structure is used to manage individual slices of the overall read
205 A pointer to the read request.
210 The file position of the start of this slice of the read request and the
217 slice. If a short read occurs, the helpers will call again, having updated
218 this to reflect the amount read so far.
222 Flags pertaining to the read. There are two of interest to the filesystem
241 Read Helper Operations
244 The network filesystem must provide the read helpers with a table of operations
276 cache (if present) to initialise the caching state for this read. The netfs
290 readahead read request. The filesystem gets to expand the request in both
312 data should be read from the server.
326 [Optional] This is called to find out if the data just read from the local
351 Read Helper Procedure
354 The read helpers work by the following general procedure:
359 propose expansions to the read request. This is then proposed to the VM.
360 If the VM cannot fully perform the expansion, a partially expanded read will
371 * The helpers issue a read from the cache or a read from the server or just
376 * As slices finish being read, they terminate.
390 * If NETFS_SREQ_CLEAR_TAIL was set, a short read will be cleared to the
393 * Once the data is read, the pages that have been fully read/cleared:
411 Read Helper Cache API
414 When implementing a local cache to be used by the read helpers, two things are
416 read request and a table of operations for the helpers to call.
448 int (*read)(struct netfs_cache_resources *cres,
472 [Required] Called to clean up the resources at the end of the read request.
490 downloaded from the server or read from the cache - or whether slicing
499 * ``read()``
501 [Required] Called to read from the cache. The start file offset is given
502 along with an iterator to read to, which gives the length also. It can be
524 not the read request structure as they could be used in other situations where
525 there isn't a read request structure as well, such as writing dirty data to the