Lines Matching refs:be

29 This facility is available to and expected to be be used by the cache backends,
33 To make use of this facility, <linux/fscache-cache.h> should be #included.
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
63 The op->fast_work, op->slow_work and op->processor flags should be set as
66 FSCACHE_OP_WAITING may be set in op->flags prior to each submission of the
74 There are a number of parameters that can be set in the operation record's flag
78  (1) The operation may be done synchronously (FSCACHE_OP_MYTHREAD).  A thread
88      If this option is to be used, FSCACHE_OP_WAITING must be set in op->flags
90      to be cleared before proceeding:
96  (2) The operation may be fast asynchronous (FSCACHE_OP_FAST), in which case it
97      will be given to keventd to process.  Such an operation is not permitted
103      If this option is used, op->fast_work and op->processor must be
109  (3) The operation may be slow asynchronous (FSCACHE_OP_SLOW), in which case it
110      will be given to the slow work facility to process.  Such an operation is
116      If this option is used, op->slow_work and op->processor must be
122 Furthermore, operations may be one of two types:
130  (2) Shareable.  Operations of this type may be running simultaneously.  It's
142      itself.  Normally this would be part of a more specific structure with the
154      The first function should be used to submit non-exclusive ops and the
159      object and return 0.  -ENOBUFS will be returned if the object specified is
163      undergoing lookup or creation.  The operation will also be deferred if an
180      exclusive ops conflicting until it is released.  The operation can be
191      This can be used to allow other things to have use of the worker thread