From: Chris Down <chris@chrisdown.name>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>, Roman Gushchin <guro@fb.com>,
Yafang Shao <laoar.shao@gmail.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/2] mm, memcg: memory.{low,min} reclaim fix & cleanup
Date: Mon, 13 Jul 2020 12:04:56 +0100 [thread overview]
Message-ID: <cover.1594638158.git.chris@chrisdown.name> (raw)
This series contains a fix for a edge case in my earlier protection
calculation patches, and a patch to make the area overall a little more
robust to hopefully help avoid this in future.
Changes in v4:
- Fix premature OOM when checking protection on root memcg. Thanks
Naresh and Michal for helping debug.
Chris Down (1):
mm, memcg: Decouple e{low,min} state mutations from protection checks
Yafang Shao (1):
mm, memcg: Avoid stale protection values when cgroup is above
protection
include/linux/memcontrol.h | 95 ++++++++++++++++++++++++++++++++------
mm/memcontrol.c | 36 ++++++---------
mm/vmscan.c | 20 +++-----
3 files changed, 103 insertions(+), 48 deletions(-)
--
2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: Chris Down <chris-6Bi1550iOqEnzZ6mRAm98g@public.gmane.org>
To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Roman Gushchin <guro-b10kYP2dOMg@public.gmane.org>,
Yafang Shao <laoar.shao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v4 0/2] mm, memcg: memory.{low,min} reclaim fix & cleanup
Date: Mon, 13 Jul 2020 12:04:56 +0100 [thread overview]
Message-ID: <cover.1594638158.git.chris@chrisdown.name> (raw)
This series contains a fix for a edge case in my earlier protection
calculation patches, and a patch to make the area overall a little more
robust to hopefully help avoid this in future.
Changes in v4:
- Fix premature OOM when checking protection on root memcg. Thanks
Naresh and Michal for helping debug.
Chris Down (1):
mm, memcg: Decouple e{low,min} state mutations from protection checks
Yafang Shao (1):
mm, memcg: Avoid stale protection values when cgroup is above
protection
include/linux/memcontrol.h | 95 ++++++++++++++++++++++++++++++++------
mm/memcontrol.c | 36 ++++++---------
mm/vmscan.c | 20 +++-----
3 files changed, 103 insertions(+), 48 deletions(-)
--
2.27.0
next reply other threads:[~2020-07-13 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 11:04 Chris Down [this message]
2020-07-13 11:04 ` [PATCH v4 0/2] mm, memcg: memory.{low,min} reclaim fix & cleanup Chris Down
2020-07-13 11:05 ` [PATCH v4 1/2] mm, memcg: Avoid stale protection values when cgroup is above protection Yafang Shao
2020-07-13 11:05 ` Yafang Shao
2020-07-13 11:06 ` [PATCH v4 2/2] mm, memcg: Decouple e{low,min} state mutations from protection checks Chris Down
2020-07-13 11:06 ` Chris Down
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=cover.1594638158.git.chris@chrisdown.name \
--to=chris@chrisdown.name \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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 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.