From: Roman Gushchin <guro@fb.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, kernel-team@fb.com,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 1/2] mm: introduce memory.min
Date: Fri, 20 Apr 2018 18:20:45 +0100 [thread overview]
Message-ID: <20180420172039.GA4965@castle.DHCP.thefacebook.com> (raw)
In-Reply-To: <527af98a-8d7f-42ab-9ba8-71444ef7e25f@infradead.org>
On Fri, Apr 20, 2018 at 10:01:04AM -0700, Randy Dunlap wrote:
> On 04/20/18 09:36, Roman Gushchin wrote:
>
> > ---
> > Documentation/cgroup-v2.txt | 20 +++++++++
> > include/linux/memcontrol.h | 15 ++++++-
> > include/linux/page_counter.h | 11 ++++-
> > mm/memcontrol.c | 99 ++++++++++++++++++++++++++++++++++++--------
> > mm/page_counter.c | 63 ++++++++++++++++++++--------
> > mm/vmscan.c | 19 ++++++++-
> > 6 files changed, 189 insertions(+), 38 deletions(-)
> >
> > diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt
> > index 657fe1769c75..49c846020f96 100644
> > --- a/Documentation/cgroup-v2.txt
> > +++ b/Documentation/cgroup-v2.txt
> > @@ -1002,6 +1002,26 @@ PAGE_SIZE multiple when read back.
> > The total amount of memory currently being used by the cgroup
> > and its descendants.
> >
> > + memory.min
> > + A read-write single value file which exists on non-root
> > + cgroups. The default is "0".
> > +
> > + Hard memory protection. If the memory usage of a cgroup
> > + is within its effectife min boundary, the cgroup's memory
>
> effective
>
> > + won't be reclaimed under any conditions. If there is no
> > + unprotected reclaimable memory available, OOM killer
> > + is invoked.
> > +
> > + Effective low boundary is limited by memory.min values of
> > + all ancestor cgroups. If there is memory.mn overcommitment
>
> memory.min ? overcommit
>
> > + (child cgroup or cgroups are requiring more protected memory,
>
> drop ending ',' ^^
>
> > + than parent will allow), then each child cgroup will get
> > + the part of parent's protection proportional to the its
>
> to its
>
> > + actual memory usage below memory.min.
> > +
> > + Putting more memory than generally available under this
> > + protection is discouraged and may lead to constant OOMs.
> > +
> > memory.low
> > A read-write single value file which exists on non-root
> > cgroups. The default is "0".
>
>
> --
> ~Randy
Hi, Randy!
An updated version below.
Thanks!
------------------------------------------------------------
next prev parent reply other threads:[~2018-04-20 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 16:36 [PATCH 1/2] mm: introduce memory.min Roman Gushchin
2018-04-20 16:36 ` [PATCH 2/2] mm: move the high field from struct mem_cgroup to page_counter Roman Gushchin
2018-04-20 20:54 ` Johannes Weiner
2018-04-23 12:41 ` Roman Gushchin
2018-04-20 17:01 ` [PATCH 1/2] mm: introduce memory.min Randy Dunlap
2018-04-20 17:20 ` Roman Gushchin [this message]
2018-04-20 17:29 ` Randy Dunlap
2018-04-20 20:44 ` Johannes Weiner
2018-04-23 12:44 ` Roman Gushchin
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=20180420172039.GA4965@castle.DHCP.thefacebook.com \
--to=guro@fb.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.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).