Lines Matching refs:policy

8 Mappings are loaded into the policy at construction time.
10 Every bio that is mapped by the target is referred to the policy.
11 The policy can return a simple HIT or MISS or issue a migration.
13 Currently there's no way for the policy to issue background work,
17 Because we map bios, rather than requests it's easy for the policy
19 issues periodic ticks to the policy.  It's suggested that the policy
31 This policy has been deprecated in favor of the smq policy (see below).
33 The multiqueue policy has three sets of 16 queues: one set for entries
39 on hit count on entry. The policy aims to take different cache miss
67 Internally the mq policy determines a promotion threshold.  If the hit
79 This policy is the default.
81 The stochastic multi-queue (smq) policy addresses some of the problems
82 with the multiqueue (mq) policy.
84 The smq policy (vs mq) offers the promise of less memory utilization,
90 mq policy's hints to be dropped.  Also, performance of the cache may
95 The mq policy uses a lot of memory; 88 bytes per cache block on a 64
121 The MQ policy maintains a hit count for each cache block.  For a
148 	<policy> <#policy_args> [<policy arg>]*