Lines Matching +full:cache +full:- +full:block

21 doesn't update states (eg, hit counts) for a block more than once
26 Overview of supplied cache replacement policies
30 ---------------
43 ---------------------------
47 The stochastic multi-queue (smq) policy addresses some of the problems
55 DM table that is using the cache target.  Doing so will cause all of the
56 mq policy's hints to be dropped.  Also, performance of the cache may
63 The mq policy used a lot of memory; 88 bytes per cache block on a 64
67 pointers.  It avoids storing an explicit hit count for each block.  It
68 has a 'hotspot' queue, rather than a pre-cache, which uses a quarter of
69 the entries (each hotspot block covers a larger area than a single
70 cache block).
72 All this means smq uses ~25bytes per cache block.  Still a lot of
91 The mq policy maintained a hit count for each cache block.  For a
92 different block to get promoted to the cache its hit count has to
93 exceed the lowest currently in the cache.  This meant it could take a
94 long time for the cache to adapt between varying IO patterns.
108 -------
110 The cleaner writes back all dirty blocks in a cache to decommission it.
117 	cache <metadata dev> <cache dev> <origin dev> <block size>
128 	dmsetup create blah --table "0 268435456 cache /dev/sdb /dev/sdc \