From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org, Gerald Schaefer <gerald.schaefer@de.ibm.com>
Subject: Re: [PATCH 2/4] lsmem: new tool
Date: Thu, 3 Nov 2016 17:19:48 +0100 [thread overview]
Message-ID: <20161103161948.GA12234@osiris> (raw)
In-Reply-To: <20161103120059.75nflzf5wvepafzu@ws.net.home>
On Thu, Nov 03, 2016 at 01:00:59PM +0100, Karel Zak wrote:
> On Wed, Oct 12, 2016 at 02:00:45PM +0200, Heiko Carstens wrote:
> > RANGE SIZE STATE REMOVABLE BLOCK
> > 0x0000000000000000-0x000000005fffffff 1,5G online yes 0-5
> > 0x0000000060000000-0x000000007fffffff 512M online no 6-7
> > 0x0000000080000000-0x000000013fffffff 3G online yes 8-19
> > 0x0000000140000000-0x000000014fffffff 256M offline - 20
> > 0x0000000150000000-0x000000017fffffff 768M online no 21-23
> >
> > Memory block size : 256M
> > Total online memory : 5,8G
> > Total offline memory: 256M
>
> It seems that for backward compatibility we need the summary lines at
> the end. Maybe we can add --no-summary and --summary-only for people
> who want to use it in the scripts.
Scripts should use the --parsable option (or one of the new options you
mentioned below), no?
However it's of course fine with me to make the summary lines optional.
> > The lsmem tool also has "--extendend" and "--parsable" option which
> > can be used to customize the output, e.g. limit the output to
> > specified columns. This is quite similar to what the lscpu tool does.
>
> Frankly, I don't like these lscpu options :-) For new tools we have
> --pairs/export (NAME=value), --raw, --json and --output=<list>.
>
> You do not need to re-submit the patches, I'll cleanup the stuff.
Also fine with me :) Thank you for taking care of this!
next prev parent reply other threads:[~2016-11-03 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 12:00 [PATCH 0/4] New tools lsmem and chmem Heiko Carstens
2016-10-12 12:00 ` [PATCH 1/4] lib,strutils: add strtoux[16|32|64]_or_err functions Heiko Carstens
2016-10-12 12:00 ` [PATCH 2/4] lsmem: new tool Heiko Carstens
2016-11-03 12:00 ` Karel Zak
2016-11-03 16:19 ` Heiko Carstens [this message]
2016-11-04 10:39 ` Karel Zak
2016-11-04 12:10 ` Heiko Carstens
2016-11-09 9:16 ` Karel Zak
2016-10-12 12:00 ` [PATCH 3/4] chmem: " Heiko Carstens
2016-10-19 10:40 ` Heiko Carstens
2016-10-12 12:00 ` [PATCH 4/4] lsmem: add testcase Heiko Carstens
2016-10-19 9:38 ` [PATCH 0/4] New tools lsmem and chmem Karel Zak
2016-10-19 9:59 ` Heiko Carstens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161103161948.GA12234@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox