From: Johannes Weiner <hannes@cmpxchg.org>
To: Chris Down <chris@chrisdown.name>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>, Tejun Heo <tj@kernel.org>,
Roman Gushchin <guro@fb.com>, Dennis Zhou <dennis@kernel.org>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-mm@kvack.org, kernel-team@fb.com
Subject: Re: [PATCH v2 2/2] mm: Consider subtrees in memory.events
Date: Mon, 11 Feb 2019 14:01:15 -0500 [thread overview]
Message-ID: <20190211190115.GC13953@cmpxchg.org> (raw)
In-Reply-To: <20190208224419.GA24772@chrisdown.name>
On Fri, Feb 08, 2019 at 10:44:19PM +0000, Chris Down wrote:
> memory.stat and other files already consider subtrees in their output,
> and we should too in order to not present an inconsistent interface.
>
> The current situation is fairly confusing, because people interacting
> with cgroups expect hierarchical behaviour in the vein of memory.stat,
> cgroup.events, and other files. For example, this causes confusion when
> debugging reclaim events under low, as currently these always read "0"
> at non-leaf memcg nodes, which frequently causes people to misdiagnose
> breach behaviour. The same confusion applies to other counters in this
> file when debugging issues.
>
> Aggregation is done at write time instead of at read-time since these
> counters aren't hot (unlike memory.stat which is per-page, so it does it
> at read time), and it makes sense to bundle this with the file
> notifications.
>
> After this patch, events are propagated up the hierarchy:
>
> [root@ktst ~]# cat /sys/fs/cgroup/system.slice/memory.events
> low 0
> high 0
> max 0
> oom 0
> oom_kill 0
> [root@ktst ~]# systemd-run -p MemoryMax=1 true
> Running as unit: run-r251162a189fb4562b9dabfdc9b0422f5.service
> [root@ktst ~]# cat /sys/fs/cgroup/system.slice/memory.events
> low 0
> high 0
> max 7
> oom 1
> oom_kill 1
>
> As this is a change in behaviour, this can be reverted to the old
> behaviour by mounting with the `memory_localevents` flag set. However,
> we use the new behaviour by default as there's a lack of evidence that
> there are any current users of memory.events that would find this change
> undesirable.
>
> Signed-off-by: Chris Down <chris@chrisdown.name>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Roman Gushchin <guro@fb.com>
> Cc: Dennis Zhou <dennis@kernel.org>
> Cc: linux-kernel@vger.kernel.org
> Cc: cgroups@vger.kernel.org
> Cc: linux-mm@kvack.org
> Cc: kernel-team@fb.com
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
next prev parent reply other threads:[~2019-02-11 19:01 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 22:31 [PATCH " Chris Down
2019-01-24 0:24 ` Roman Gushchin
2019-01-24 1:03 ` Chris Down
2019-01-24 8:22 ` Michal Hocko
2019-01-24 15:21 ` Tejun Heo
2019-01-24 15:51 ` Michal Hocko
2019-01-24 16:00 ` Johannes Weiner
2019-01-24 17:01 ` Michal Hocko
2019-01-24 18:23 ` Johannes Weiner
2019-01-25 8:42 ` Michal Hocko
2019-01-25 16:51 ` Tejun Heo
2019-01-25 17:37 ` Michal Hocko
2019-01-25 17:37 ` Michal Hocko
2019-01-25 18:28 ` Tejun Heo
2019-01-28 12:51 ` Michal Hocko
2019-01-28 14:28 ` Tejun Heo
2019-01-28 14:52 ` Michal Hocko
2019-01-28 14:54 ` Tejun Heo
2019-01-28 15:18 ` Michal Hocko
2019-01-28 15:41 ` Tejun Heo
2019-01-28 17:05 ` Michal Hocko
2019-01-28 17:05 ` Michal Hocko
2019-01-28 17:49 ` Tejun Heo
2019-01-28 17:49 ` Tejun Heo
2019-01-29 14:43 ` Michal Hocko
2019-01-29 14:52 ` Tejun Heo
2019-01-30 16:50 ` Michal Hocko
2019-01-30 17:06 ` Tejun Heo
2019-01-30 17:41 ` Michal Hocko
2019-01-30 17:52 ` Tejun Heo
2019-01-30 18:16 ` Michal Hocko
2019-01-30 19:11 ` Shakeel Butt
2019-01-30 19:27 ` Johannes Weiner
2019-01-30 19:30 ` Johannes Weiner
2019-01-30 19:37 ` Shakeel Butt
2019-01-30 19:23 ` Johannes Weiner
2019-01-30 20:05 ` Michal Hocko
2019-01-30 21:31 ` Johannes Weiner
2019-01-31 8:58 ` Michal Hocko
2019-01-31 16:22 ` Johannes Weiner
2019-02-01 10:27 ` Michal Hocko
2019-02-01 16:34 ` Johannes Weiner
2019-01-28 15:59 ` Shakeel Butt
2019-01-28 15:59 ` Shakeel Butt
2019-01-28 16:05 ` Tejun Heo
2019-01-28 16:05 ` Tejun Heo
2019-01-28 16:08 ` Shakeel Butt
2019-01-28 16:08 ` Shakeel Butt
2019-01-28 16:12 ` Tejun Heo
2019-01-28 16:12 ` Tejun Heo
2019-01-28 14:30 ` Tejun Heo
2019-02-08 22:43 ` [PATCH v2 1/2] mm: Rename ambiguously named memory.stat counters and functions Chris Down
2019-02-08 22:44 ` [PATCH v2 2/2] mm: Consider subtrees in memory.events Chris Down
2019-02-11 19:01 ` Johannes Weiner [this message]
2019-02-11 18:55 ` [PATCH v2 1/2] mm: Rename ambiguously named memory.stat counters and functions 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=20190211190115.GC13953@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=dennis@kernel.org \
--cc=guro@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--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