From: Michal Hocko <mhocko@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <guro@fb.com>, Shakeel Butt <shakeelb@google.com>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
Aaron Lu <aaron.lu@intel.com>
Subject: Re: [RFC PATCH 0/2] mm/memcontrol: Finer-grained memory control
Date: Wed, 10 Apr 2019 21:54:43 +0200 [thread overview]
Message-ID: <20190410195443.GL10383@dhcp22.suse.cz> (raw)
In-Reply-To: <20190410191321.9527-1-longman@redhat.com>
On Wed 10-04-19 15:13:19, Waiman Long wrote:
> The current control mechanism for memory cgroup v2 lumps all the memory
> together irrespective of the type of memory objects. However, there
> are cases where users may have more concern about one type of memory
> usage than the others.
>
> We have customer request to limit memory consumption on anonymous memory
> only as they said the feature was available in other OSes like Solaris.
Please be more specific about a usecase.
> To allow finer-grained control of memory, this patchset 2 new control
> knobs for memory controller:
> - memory.subset.list for specifying the type of memory to be under control.
> - memory.subset.high for the high limit of memory consumption of that
> memory type.
Please be more specific about the semantic.
I am really skeptical about this feature to be honest, though.
> For simplicity, the limit is not hierarchical and applies to only tasks
> in the local memory cgroup.
This is a no-go to begin with.
> Waiman Long (2):
> mm/memcontrol: Finer-grained control for subset of allocated memory
> mm/memcontrol: Add a new MEMCG_SUBSET_HIGH event
>
> Documentation/admin-guide/cgroup-v2.rst | 35 +++++++++
> include/linux/memcontrol.h | 8 ++
> mm/memcontrol.c | 100 +++++++++++++++++++++++-
> 3 files changed, 142 insertions(+), 1 deletion(-)
>
> --
> 2.18.1
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-04-10 19:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 19:13 [RFC PATCH 0/2] mm/memcontrol: Finer-grained memory control Waiman Long
2019-04-10 19:13 ` [RFC PATCH 1/2] mm/memcontrol: Finer-grained control for subset of allocated memory Waiman Long
2019-04-10 19:13 ` [RFC PATCH 2/2] mm/memcontrol: Add a new MEMCG_SUBSET_HIGH event Waiman Long
2019-04-10 19:54 ` Michal Hocko [this message]
2019-04-11 14:02 ` [RFC PATCH 0/2] mm/memcontrol: Finer-grained memory control Waiman Long
2019-04-11 15:19 ` Michal Hocko
2019-04-11 15:24 ` Michal Hocko
2019-04-11 15:31 ` Johannes Weiner
2019-04-10 21:38 ` Chris Down
2019-04-11 14:22 ` Waiman Long
2019-04-11 14:22 ` Waiman Long
2019-04-11 21:21 ` Roman Gushchin
2019-04-11 14:37 ` Kirill Tkhai
2019-04-11 14:55 ` Waiman Long
2019-04-11 15:35 ` Kirill Tkhai
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=20190410195443.GL10383@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=ktkhai@virtuozzo.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=longman@redhat.com \
--cc=shakeelb@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.