diff options
author | mulhern <amulhern@redhat.com> | 2017-11-27 10:02:42 -0500 |
---|---|---|
committer | Mike Snitzer <snitzer@redhat.com> | 2018-01-17 09:16:09 -0500 |
commit | 1346638e5f80588dfafbf07315f72b84c2ab1113 (patch) | |
tree | 7dadd747baed3fdf872ccf120e803d82d8d1a836 | |
parent | 3716e20af5b583c3e15661aab657168176baa01e (diff) | |
download | linux-1346638e5f80588dfafbf07315f72b84c2ab1113.tar.bz2 |
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>
-rw-r--r-- | Documentation/device-mapper/cache.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/device-mapper/cache.txt b/Documentation/device-mapper/cache.txt index 043524409221..79c7b6dc88ae 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 ------------------------- |