summaryrefslogtreecommitdiffstats
path: root/sys-utils/lsmem.1
diff options
context:
space:
mode:
authorKarel Zak2017-10-18 13:16:09 +0200
committerKarel Zak2017-10-20 12:37:04 +0200
commit87a24d85f5fcd7c48137d67067a3ea8c997833de (patch)
treeff4e0a5af0f5d849c5e81b59c6540608850b897d /sys-utils/lsmem.1
parentlsmem: improve path_read_xxx() usage (diff)
downloadkernel-qcow2-util-linux-87a24d85f5fcd7c48137d67067a3ea8c997833de.tar.gz
kernel-qcow2-util-linux-87a24d85f5fcd7c48137d67067a3ea8c997833de.tar.xz
kernel-qcow2-util-linux-87a24d85f5fcd7c48137d67067a3ea8c997833de.zip
lsmem: add hint about block merges to the man page
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'sys-utils/lsmem.1')
-rw-r--r--sys-utils/lsmem.15
1 files changed, 5 insertions, 0 deletions
diff --git a/sys-utils/lsmem.1 b/sys-utils/lsmem.1
index e7df50a4e..c664273f0 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