redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

dm cache: be consistent in specifying sectors and SI units in cache.txt 

Signed-off-by: mulhern <amulhern@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
hifive-unleashed-5.1
mulhern 2017-11-27 10:02:42 -05:00 committed by Mike Snitzer
parent 3716e20af5
commit 1346638e5f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/device-mapper/cache.txt
View File

@ -59,7 +59,7 @@ Fixed block size
The origin is divided up into blocks of a fixed size. This 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 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 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 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 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>" For the time being, a message "migration_threshold <#sectors>"
can be used to set the maximum number of sectors being migrated, 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 Updating on-disk metadata
------------------------- -------------------------