From: Karel Zak <kzak@redhat.com>
To: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Cc: util-linux@vger.kernel.org, Michal Hocko <mhocko@kernel.org>,
linux-mm <linux-mm@kvack.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Andre Wild <wild@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/3] lsmem/chmem: add memory zone awareness
Date: Fri, 20 Oct 2017 12:45:14 +0200 [thread overview]
Message-ID: <20171020104514.z6bsu5vx5hgh46v5@ws.net.home> (raw)
In-Reply-To: <20170927174446.20459-1-gerald.schaefer@de.ibm.com>
On Wed, Sep 27, 2017 at 07:44:43PM +0200, Gerald Schaefer wrote:
> These patches are against lsmem/chmem in util-linux, they add support
> for listing and changing memory zone allocation.
>
> Added Michal Hocko and linux-mm on cc, to raise general awareness for
> the lsmem/chmem tools, and the new memory zone functionality in
> particular. I think this can be quite useful for memory hotplug kernel
> development, and if not, sorry for the noise.
>
> Andre Wild (1):
> lsmem/chmem: add memory zone awareness to bash-completion
>
> Gerald Schaefer (2):
> lsmem/chmem: add memory zone awareness
> tests/lsmem: update lsmem test with ZONES column
Merged to the master branch.
I have added a new --split=<list> command line option to the lsmem.
It allows to control the way how lsmem merges memory blocks to the
ranges. The default is to use differences in STATE,REMOVABLE,NODE and
ZONES attributes. The ranges are no more affected by --output, it
means commands like
lsmem --output=RANGE
lsmem --output=RANGE,ZONES
returns the same memory ranges. You have to use --split to define your
policy:
lsmem --split=REMOVABLE,STATE
will create the ranges according to REMOVABLE and STATE attributes.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2017-10-20 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 17:44 [PATCH 0/3] lsmem/chmem: add memory zone awareness Gerald Schaefer
2017-09-27 17:44 ` [PATCH 1/3] " Gerald Schaefer
2017-09-27 17:44 ` [PATCH 2/3] tests/lsmem: update lsmem test with ZONES column Gerald Schaefer
2017-09-27 17:44 ` [PATCH 3/3] lsmem/chmem: add memory zone awareness to bash-completion Gerald Schaefer
2017-10-02 11:12 ` [PATCH 0/3] lsmem/chmem: add memory zone awareness Karel Zak
2017-10-18 11:40 ` Karel Zak
2017-11-02 16:54 ` Gerald Schaefer
2017-11-03 10:11 ` Karel Zak
2017-11-03 13:31 ` Gerald Schaefer
2017-10-20 10:45 ` Karel Zak [this message]
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=20171020104514.z6bsu5vx5hgh46v5@ws.net.home \
--to=kzak@redhat.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=util-linux@vger.kernel.org \
--cc=wild@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).