Lines Matching refs:be

33 may be out of date or kept in sync with the copy on the cache device
51    This information could be put on the cache device, but having it
54    be used by a single cache device.
61 using block sizes of 256KB - 1024KB.  The block size must be between 64
65 something of a compromise.  For instance, a small part of a block may be
66 getting hit a lot, yet the whole block will be promoted to the cache.
78 cached will go only to the cache and the block will be marked dirty in
86 to be coherent with the origin device, then all reads are served from
89 block invalidates.  To enable passthrough mode the cache must be clean.
90 Passthrough mode allows a cache device to be activated without having to
93 the cache can later be verified, or established through use of the
94 "invalidate_cblocks" message, the cache device can be transitioned to
96 contents can be discarded prior to transitioning to the desired
102 blocks, in the area of the cache being removed, to be clean.  If the
104 will fail.  Care must be taken to never reduce the volume used for the
121 can be used to set the maximum number of sectors being migrated,
131 should always be consistent in spite of any crash.
135 operation it will be written when the dm device is suspended.  If the
136 system crashes all cache blocks will be assumed dirty when restarted.
142 the policy how big this chunk is, but it should be kept small.  Like the
144 value should always be possible.
148 there's a crash this information will be lost, which means the cache
149 may be less efficient until those hit counts are regenerated.
208 		   To enable passthrough mode the cache must be clean.
250 #core args		 : Number of core arguments (must be even)
254 #policy args		 : Number of policy arguments to follow (must be even)
258 	no further I/O will be permitted and the status will just
260 	should then be used.
264 	device must be deactivated and checked/repaired before the
265 	cache can be made fully operational again.  '-' indicates
273 messages are used.  (A sysfs interface would also be possible.)
284 back.  Cache blocks can be invalidated via the invalidate_cblocks
287 of values from 5 to 9.  Each cblock must be expressed as a decimal
289 expressed in hexidecimal may be needed to better support efficient
290 invalidation of larger caches.  The cache must be in passthrough mode
301 The test suite can be found here: