All of lore.kernel.org
 help / color / mirror / Atom feed
From: amulhern@redhat.com
To: dm-devel@redhat.com
Cc: mulhern <amulhern@redhat.com>, snitzer@redhat.com
Subject: [PATCH 3/7] dm: documentation fix
Date: Mon, 27 Nov 2017 10:02:41 -0500	[thread overview]
Message-ID: <20171127150245.27959-3-amulhern@redhat.com> (raw)
In-Reply-To: <20171127150245.27959-1-amulhern@redhat.com>

From: mulhern <amulhern@redhat.com>

Delete obsoleted paragraph

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>
---
 Documentation/device-mapper/cache.txt | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/Documentation/device-mapper/cache.txt b/Documentation/device-mapper/cache.txt
index cdfd0fe..0435244 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
-- 
2.9.5

  parent reply	other threads:[~2017-11-27 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 15:02 [PATCH 1/7] dm: documentation fix amulhern
2017-11-27 15:02 ` [PATCH 2/7] " amulhern
2017-11-27 15:02 ` amulhern [this message]
2017-11-27 15:02 ` [PATCH 4/7] " amulhern
2017-11-27 15:02 ` [PATCH 5/7] " amulhern
2017-11-27 15:02 ` [PATCH 6/7] " amulhern
2017-11-27 15:02 ` [PATCH 7/7] " amulhern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171127150245.27959-3-amulhern@redhat.com \
    --to=amulhern@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=snitzer@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.