Lines Matching refs:blocks
49 3. A small metadata device - records which blocks are in the cache,
59 The origin is divided up into blocks of a fixed size. This block size
83 blocks should remain clean.
100 dirty blocks in a cache. Useful for decommissioning a cache or when
102 blocks, in the area of the cache being removed, to be clean. If the
103 area being removed from the cache still contains dirty blocks the resize
136 system crashes all cache blocks will be assumed dirty when restarted.
147 uses this facility to store the hit count of the cache blocks. If
166 blocks. However, we allow this bitset to have a different block size
167 from the cache blocks. This is because we need to track the discard
182 cache dev : fast device holding cached data blocks
183 origin dev : slow device holding original data blocks
201 so they may differ from the corresponding origin blocks.
219 <metadata block size> <#used metadata blocks>/<#total metadata blocks>
220 <cache block size> <#used cache blocks>/<#total cache blocks>
227 #used metadata blocks : Number of metadata blocks used
228 #total metadata blocks : Total number of metadata blocks
231 #used cache blocks : Number of blocks resident in the cache
232 #total cache blocks : Total number of cache blocks
245 #dirty : Number of blocks in the cache that differ
273 back. Cache blocks can be invalidated via the invalidate_cblocks