Lines Matching full:request

111  * Allow the netfs to expand a readahead request in both directions to meet its
117    interleaved for a single request.
157 The helpers manage the read request, calling back into the network filesystem
162 netfs_io_request struct allocated.  If some parts of the request are in
163 progress when an error occurs, the request will get partially completed if
182 the read.  The first is a structure that manages a read request as a whole::
212    to the helper functions or set during the request.
217    The file position of the start of the read request and the length.  These
222    The size of the file at the start of the request.
236 request::
253    A pointer to the read request.
258    The file position of the start of this slice of the read request and the
311    [Optional] This is called to initialise the request structure.  It is given
316    [Optional] This is called as the request is being deallocated so that the
322    readahead read request.  The filesystem gets to expand the request in both
325    to expand the request first.
327    Expansion is communicated by changing ->start and ->len in the request
334    subrequest.  The filesystem can use this, for example, to chop up a request
376    [Optional] This is called after the folios in the request have all been
386  * Set up the request.
389    propose expansions to the read request.  This is then proposed to the VM.
393  * Loop around slicing chunks off of the request to form subrequests:
438  * The request structures will be cleaned up when everything has completed.
446 read request and a table of operations for the helpers to call.
454 passing in the request pointer and the cookie corresponding to the file.  This
510    [Required] Called to clean up the resources at the end of the read request.
515    the cache to expand a request in either direction.  This allows the cache to
516    size the request appropriately for the cache granularity.
533    [Required] Called to configure the next slice of a request.  ->start and
585 not the read request structure as they could be used in other situations where
586 there isn't a read request structure as well, such as writing dirty data to the