dm cache: switch the "default" cache replacement policy from mq to smq
authorMike Snitzer <snitzer@redhat.com>
Wed, 17 Jun 2015 15:43:38 +0000 (11:43 -0400)
committerMike Snitzer <snitzer@redhat.com>
Wed, 17 Jun 2015 16:40:38 +0000 (12:40 -0400)
commitbccab6a01afc26f53d91762d78153513cad10b29
treea93caf5032b84668099e2ab35b7593cada04113c
parent6096d91af0b65a3967139b32d5adbb3647858a26
dm cache: switch the "default" cache replacement policy from mq to smq

The Stochastic multiqueue (SMQ) policy (vs MQ) offers the promise of
less memory utilization, improved performance and increased adaptability
in the face of changing workloads.  SMQ also does not have any
cumbersome tuning knobs.

Users may switch from "mq" to "smq" simply by appropriately reloading a
DM table that is using the cache target.  Doing so will cause all of the
mq policy's hints to be dropped.  Also, performance of the cache may
degrade slightly until smq recalculates the origin device's hotspots
that should be cached.

In the future the "mq" policy will just silently make use of "smq" and
the mq code will be removed.

Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Acked-by: Joe Thornber <ejt@redhat.com>
Documentation/device-mapper/cache-policies.txt
drivers/md/dm-cache-policy-mq.c
drivers/md/dm-cache-policy-smq.c