summaryrefslogtreecommitdiffstats
path: root/Documentation/device-mapper
diff options
context:
space:
mode:
authormulhern <amulhern@redhat.com>2017-11-27 10:02:41 -0500
committerMike Snitzer <snitzer@redhat.com>2018-01-17 09:16:08 -0500
commit3716e20af5b583c3e15661aab657168176baa01e (patch)
tree1a06ff469ffca718429cee984d1f541589eb194b /Documentation/device-mapper
parent677210462daf48dbf69a5bd2e38deb271d1a41bf (diff)
downloadlinux-3716e20af5b583c3e15661aab657168176baa01e.tar.bz2
dm cache: delete obsoleted paragraph in cache.txt
The 'mq' policy is no longer the default policy, and the default policy, 'smq', does not store hit counts. Signed-off-by: mulhern <amulhern@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'Documentation/device-mapper')
-rw-r--r--Documentation/device-mapper/cache.txt5
1 files changed, 0 insertions, 5 deletions
diff --git a/Documentation/device-mapper/cache.txt b/Documentation/device-mapper/cache.txt
index cdfd0feb294e..043524409221 100644
--- a/Documentation/device-mapper/cache.txt
+++ b/Documentation/device-mapper/cache.txt
@@ -143,11 +143,6 @@ the policy how big this chunk is, but it should be kept small. Like the
dirty flags this data is lost if there's a crash so a safe fallback
value should always be possible.
-For instance, the 'mq' policy, which is currently the default policy,
-uses this facility to store the hit count of the cache blocks. If
-there's a crash this information will be lost, which means the cache
-may be less efficient until those hit counts are regenerated.
-
Policy hints affect performance, not correctness.
Policy messaging