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>
This commit is contained in:
Родитель
3716e20af5
Коммит
1346638e5f
|
@ -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
|
||||||
-------------------------
|
-------------------------
|
||||||
|
|
Загрузка…
Ссылка в новой задаче