Lines Matching refs:to

29 This facility is available to and expected to be be used by the cache backends,
30 and FS-Cache will create operations and pass them off to the appropriate cache
52 Someone wanting to issue an operation should allocate something with this
58 with the operation to be initialised and the release function to use.
60 The op->flags parameter should be set to indicate the CPU time provision and
66 FSCACHE_OP_WAITING may be set in op->flags prior to each submission of the
79      may decide it wants to handle an operation itself without deferring it to
88      If this option is to be used, FSCACHE_OP_WAITING must be set in op->flags
90      to be cleared before proceeding:
97      will be given to keventd to process.  Such an operation is not permitted
98      to sleep on I/O.
100      This is, for example, used by CacheFiles to copy data from a backing fs
101      page to a netfs page after the backing fs has read the page in.
110      will be given to the slow work facility to process.  Such an operation is
111      permitted to sleep on I/O.
113      This is, for example, used by FS-Cache to handle background writes of
128      being written to may need truncation.
131      up to the operation implementation to prevent interference between other
154      The first function should be used to submit non-exclusive ops and the
155      second to submit exclusive ones.  The caller must still set the
158      If successful, both functions will assign the operation to the specified
166      If the operation is asynchronous, the manager will retain a reference to
167      it, so the caller should put their reference to it by passing it to:
171  (3) If the submitting thread wants to do the work itself, and has marked the
191      This can be used to allow other things to have use of the worker thread
200 processor method with a pointer to the operation.  This should then get at the
212 function is at liberty to call fscache_enqueue_operation() or to take extra