From d12e945dbf7758e43ec4aaadd0c8c28c1269236e Mon Sep 17 00:00:00 2001 From: Karel Zak Date: Fri, 20 Oct 2017 12:31:09 +0200 Subject: 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 --- sys-utils/chmem.8 | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'sys-utils/chmem.8') 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-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. 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 - or as shown in the -- cgit v1.2.3-55-g7522