Patchwork [4/7] dm: documentation fix

login
register
mail settings
Submitter amulhern@redhat.com
Date Nov. 27, 2017, 3:02 p.m.
Message ID <20171127150245.27959-4-amulhern@redhat.com>
Download mbox | patch
Permalink /patch/10076987/
State Accepted, archived
Delegated to: Mike Snitzer
Headers show

Comments

amulhern@redhat.com - Nov. 27, 2017, 3:02 p.m.
From: mulhern <amulhern@redhat.com>

Be consistent in specifying sectors and SI units

Signed-off-by: mulhern <amulhern@redhat.com>
---
 Documentation/device-mapper/cache.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Patch

diff --git a/Documentation/device-mapper/cache.txt b/Documentation/device-mapper/cache.txt
index 0435244..79c7b6d 100644
--- a/Documentation/device-mapper/cache.txt
+++ b/Documentation/device-mapper/cache.txt
@@ -59,7 +59,7 @@  Fixed block size
 The origin is divided up into blocks of a fixed size.  This block size
 is configurable when you first create the cache.  Typically we've been
 using block sizes of 256KB - 1024KB.  The block size must be between 64
-(32KB) and 2097152 (1GB) and a multiple of 64 (32KB).
+sectors (32KB) and 2097152 sectors (1GB) and a multiple of 64 sectors (32KB).
 
 Having a fixed block size simplifies the target a lot.  But it is
 something of a compromise.  For instance, a small part of a block may be
@@ -119,7 +119,7 @@  doing here to avoid migrating during those peak io moments.
 
 For the time being, a message "migration_threshold <#sectors>"
 can be used to set the maximum number of sectors being migrated,
-the default being 204800 sectors (or 100MB).
+the default being 204800 sectors (100MB).
 
 Updating on-disk metadata
 -------------------------