From: Balbir Singh <bsingharora@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
mpe@ellerman.id.au, akpm@linux-foundation.org
Subject: Re: [v1 0/3] Support memory cgroup hotplug
Date: Wed, 16 Nov 2016 10:47:26 +1100 [thread overview]
Message-ID: <ac99835c-ae55-f1e2-f449-cd1bd9585806@gmail.com> (raw)
In-Reply-To: <20161115154219.GA28262@htj.duckdns.org>
On 16/11/16 02:42, Tejun Heo wrote:
> Hello, Balbir.
>
> On Tue, Nov 15, 2016 at 10:44:02AM +1100, 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.
>>
>> Cc: Tejun Heo <tj@kernel.org>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>
> Can you please cc memcg maintainers? Johannes Weiner
> <hannes@cmpxchg.org>, Michal Hocko <mhocko@kernel.org> and Vladimir
> Davydov <vdavydov.dev@gmail.com>.
>
> Thanks.
>
My bad - resent with copies to the recommended maintainers.
Thanks,
Balbir Singh.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-11-15 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 23:44 [v1 0/3] Support memory cgroup hotplug Balbir Singh
2016-11-14 23:44 ` [PATCH v1 1/3] Add basic infrastructure for memcg hotplug support Balbir Singh
2016-11-14 23:44 ` [PATCH v1 2/3] Move from all possible nodes to online nodes Balbir Singh
2016-11-14 23:44 ` [PATCH v1 3/3] powerpc: fix node_possible_map limitations Balbir Singh
2016-11-15 7:00 ` Michael Ellerman
2016-11-15 15:42 ` [v1 0/3] Support memory cgroup hotplug Tejun Heo
2016-11-15 23:47 ` Balbir Singh [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=ac99835c-ae55-f1e2-f449-cd1bd9585806@gmail.com \
--to=bsingharora@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).