From: Michal Hocko <mhocko@kernel.org>
To: Balbir Singh <bsingharora@gmail.com>
Cc: linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [mm v2 0/3] Support memory cgroup hotplug
Date: Wed, 23 Nov 2016 08:25:44 +0100 [thread overview]
Message-ID: <20161123072543.GD2864@dhcp22.suse.cz> (raw)
In-Reply-To: <1479875814-11938-1-git-send-email-bsingharora@gmail.com>
On Wed 23-11-16 15:36:51, Balbir Singh wrote:
> In the absence of hotplug we use extra memory proportional to
> (possible_nodes - online_nodes) * number_of_cgroups. PPC64 has a patch
> to disable large consumption with large number of cgroups. This patch
> adds hotplug support to memory cgroups and reverts the commit that
> limited possible nodes to online nodes.
Balbir,
I have asked this in the previous version but there still seems to be a
lack of information of _why_ do we want this, _how_ much do we save on
the memory overhead on most systems and _why_ the additional complexity
is really worth it. Please make sure to add all this in the cover
letter.
I still didn't get to look into those patches because I am swamped with
other things but to be honest I do not really see a strong justification
to make it high priority for me.
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
>
> I've tested this patches under a VM with two nodes and movable
> nodes enabled. I've offlined nodes and checked that the system
> and cgroups with tasks deep in the hierarchy continue to work
> fine.
>
> These patches are on top of linux-next (20161117)
>
> Changelog v2:
> Add get/put_online_mems() around node iteration
> Use MEM_OFFLINE/MEM_ONLINE instead of MEM_GOING_OFFLINE/ONLINE
>
> Balbir Singh (3):
> mm: Add basic infrastructure for memcg hotplug support
> mm: Move operations to hotplug callbacks
> powerpc/mm: fix node_possible_map limitations
>
> arch/powerpc/mm/numa.c | 7 ----
> mm/memcontrol.c | 107 +++++++++++++++++++++++++++++++++++++++++++------
> 2 files changed, 94 insertions(+), 20 deletions(-)
>
> --
> 2.5.5
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-11-23 7:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 4:36 [mm v2 0/3] Support memory cgroup hotplug Balbir Singh
2016-11-23 4:36 ` [mm v2 1/3] mm: Add basic infrastructure for memcg hotplug support Balbir Singh
2016-11-23 4:36 ` [mm v2 2/3] mm: Move operations to hotplug callbacks Balbir Singh
2016-11-23 4:36 ` [mm v2 3/3] powerpc/mm: fix node_possible_map limitations Balbir Singh
2016-11-23 7:25 ` Michal Hocko [this message]
2016-11-23 7:50 ` [mm v2 0/3] Support memory cgroup hotplug Balbir Singh
2016-11-23 8:07 ` Michal Hocko
2016-11-23 8:37 ` Balbir Singh
2016-11-23 9:28 ` Michal Hocko
2016-11-23 13:05 ` Balbir Singh
2016-11-23 13:22 ` Michal Hocko
2016-11-28 21:10 ` Tejun Heo
2016-11-29 0:09 ` Balbir Singh
2016-11-29 0:42 ` Tejun Heo
2016-11-29 4:57 ` Balbir Singh
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=20161123072543.GD2864@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.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).