diff options
| author | Karel Zak | 2017-10-20 12:31:09 +0200 |
|---|---|---|
| committer | Karel Zak | 2017-10-20 12:37:04 +0200 |
| commit | d12e945dbf7758e43ec4aaadd0c8c28c1269236e (patch) | |
| tree | a0aecdad06053c8e857e425518b711b709cd8551 /sys-utils/chmem.8 | |
| parent | lsmem: add hint about block merges to the man page (diff) | |
| download | kernel-qcow2-util-linux-d12e945dbf7758e43ec4aaadd0c8c28c1269236e.tar.gz kernel-qcow2-util-linux-d12e945dbf7758e43ec4aaadd0c8c28c1269236e.tar.xz kernel-qcow2-util-linux-d12e945dbf7758e43ec4aaadd0c8c28c1269236e.zip | |
lsmem: add --split
Now the way how lsmem lists memory ranges is affected by used output
columns. It makes it very difficult to use in scripts where you want
to use for example only one column
ranges=$(lsmem -oRANGE)
and in this case all is merged to the one (or two) huge ranges and all
attributes are ignored. The --split allows to control this behavior
ranges=$(lsmem -oRANGE --split=STATE,ZONES)
forces lsmem to list ranges by STATE and ZONES differences.
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'sys-utils/chmem.8')
| -rw-r--r-- | sys-utils/chmem.8 | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/sys-utils/chmem.8 b/sys-utils/chmem.8 index b37ee8382..dae7413d4 100644 --- a/sys-utils/chmem.8 +++ b/sys-utils/chmem.8 @@ -17,8 +17,7 @@ in GiB (1024 x 1024 x 1024 bytes). The default unit is MiB. .IP "\(hy" 2 Specify \fIRANGE\fP in the form 0x<start>-0x<end> as shown in the output of the \fBlsmem\fP command. <start> is the hexadecimal address of the first byte and <end> -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). +is the hexadecimal address of the last byte in the memory range. . .IP "\(hy" 2 Specify \fIBLOCKRANGE\fP in the form <first>-<last> or <block> as shown in the |