From: Johannes Weiner <hannes@cmpxchg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.cz>, Tejun Heo <tj@kernel.org>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [patch 0/4] mm: memcontrol: populate unified hierarchy interface
Date: Mon, 4 Aug 2014 17:14:53 -0400 [thread overview]
Message-ID: <1407186897-21048-1-git-send-email-hannes@cmpxchg.org> (raw)
Hi,
the ongoing versioning of the cgroup user interface gives us a chance
to clean up the memcg control interface and fix a lot of
inconsistencies and ugliness that crept in over time.
This series adds a minimal set of control files to the new memcg
interface to get basic memcg functionality going in unified hierarchy:
- memory.current: a read-only file that shows current memory usage.
- memory.high: a file that allows setting a high limit on the memory
usage. This is an elastic limit, which is enforced via direct
reclaim, so allocators are throttled once it's reached, but it can
be exceeded and does not trigger OOM kills. This should be a much
more suitable default upper boundary for the majority of use cases
that are better off with some elasticity than with sudden OOM kills.
- memory.max: a file that allows setting a maximum limit on memory
usage which is ultimately enforced by OOM killing tasks in the
group. This is for setups that want strict isolation at the cost of
task death above a certain point. However, even those can still
combine the max limit with the high limit to approach OOM situations
gracefully and with time to intervene.
- memory.vmstat: vmstat-style per-memcg statistics. Very minimal for
now (lru stats, allocations and frees, faults), but fixing
fundamental issues of the old memory.stat file, including gross
misnomers like pgpgin/pgpgout for pages charged/uncharged etc.
Documentation/cgroups/unified-hierarchy.txt | 18 +++
include/linux/res_counter.h | 29 +++++
include/linux/swap.h | 3 +-
kernel/res_counter.c | 3 +
mm/memcontrol.c | 177 +++++++++++++++++++++++++---
mm/vmscan.c | 3 +-
6 files changed, 216 insertions(+), 17 deletions(-)
--
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>
next reply other threads:[~2014-08-04 21:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 21:14 Johannes Weiner [this message]
2014-08-04 21:14 ` [patch 1/4] mm: memcontrol: reduce reclaim invocations for higher order requests Johannes Weiner
2014-08-07 13:08 ` Michal Hocko
2014-08-07 15:31 ` Johannes Weiner
2014-08-07 16:10 ` Greg Thelen
2014-08-08 12:47 ` Michal Hocko
2014-08-08 12:32 ` Michal Hocko
2014-08-08 13:26 ` Johannes Weiner
2014-08-11 7:49 ` Michal Hocko
2014-08-13 14:59 ` Michal Hocko
2014-08-13 20:41 ` Johannes Weiner
2014-08-14 16:12 ` Michal Hocko
2014-08-04 21:14 ` [patch 2/4] mm: memcontrol: add memory.current and memory.high to default hierarchy Johannes Weiner
2014-08-07 13:36 ` Michal Hocko
2014-08-07 13:39 ` Michal Hocko
2014-08-07 15:47 ` Johannes Weiner
2014-08-04 21:14 ` [patch 3/4] mm: memcontrol: add memory.max " Johannes Weiner
2014-08-04 21:14 ` [patch 4/4] mm: memcontrol: add memory.vmstat " Johannes Weiner
2014-08-05 12:40 ` [patch 0/4] mm: memcontrol: populate unified hierarchy interface Michal Hocko
2014-08-05 13:53 ` Johannes Weiner
2014-08-05 15:27 ` Michal Hocko
2014-08-07 14:21 ` Johannes Weiner
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=1407186897-21048-1-git-send-email-hannes@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--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