From: Karel Zak Date: Wed, 18 Oct 2017 11:16:09 +0000 (+0200) Subject: lsmem: add hint about block merges to the man page X-Git-Tag: v2.32-rc1~257 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=87a24d85f5fcd7c48137d67067a3ea8c997833de;p=thirdparty%2Futil-linux.git lsmem: add hint about block merges to the man page Signed-off-by: Karel Zak --- diff --git a/sys-utils/chmem.8 b/sys-utils/chmem.8 index dae7413d48..b37ee8382f 100644 --- a/sys-utils/chmem.8 +++ b/sys-utils/chmem.8 @@ -17,7 +17,8 @@ in GiB (1024 x 1024 x 1024 bytes). The default unit is MiB. .IP "\(hy" 2 Specify \fIRANGE\fP in the form 0x-0x as shown in the output of the \fBlsmem\fP command. is the hexadecimal address of the first byte and -is the hexadecimal address of the last byte in the memory range. +is the hexadecimal address of the last byte in the memory range. Note that the range +as shown by \fBlsmem\fP command maybe be influenced by zones (\fBlsmem -o +ZONES\fP). . .IP "\(hy" 2 Specify \fIBLOCKRANGE\fP in the form - or as shown in the diff --git a/sys-utils/lsmem.1 b/sys-utils/lsmem.1 index e7df50a4eb..c664273f0c 100644 --- a/sys-utils/lsmem.1 +++ b/sys-utils/lsmem.1 @@ -18,6 +18,11 @@ together with a columns list in environments where a stable output is required. Not all columns are supported on all systems. If an unsupported column is specified, \fBlsmem\fP prints the column but does not provide any data for it. +The number of output entries (memory ranges) maybe be influenced by specified +columns. The lsmem command shows larger memory ranges if the blocks in the +range do not distinguish in output columns. For example RANGE maybe be +different if the command output contains column ZONES (lsmem -o +ZONES). + Use the \fB\-\-help\fR option to see the columns description. .SH OPTIONS