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 0/2] mm: memcontrol: memory.{low,min} reclaim fix & cleanup
Date: Tue, 28 Apr 2020 19:26:37 +0100 [thread overview]
Message-ID: <cover.1588092152.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.
Chris Down (1):
mm, memcg: Decouple e{low,min} state mutations from protection checks
Yafang Shao (1):
mm: memcontrol: memory.low reclaim fix & cleanup
include/linux/memcontrol.h | 48 +++++++++++++++++++++++++++++---------
mm/memcontrol.c | 43 ++++++++++++++++------------------
mm/vmscan.c | 17 ++++----------
3 files changed, 61 insertions(+), 47 deletions(-)
--
2.26.2
next reply other threads:[~2020-04-28 18:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 18:26 Chris Down [this message]
2020-04-28 18:26 ` [PATCH 1/2] mm, memcg: Avoid stale protection values when cgroup is above protection Chris Down
2020-04-28 21:16 ` Johannes Weiner
2020-04-29 10:15 ` Michal Hocko
2020-04-29 10:53 ` Yafang Shao
2020-04-29 14:19 ` Johannes Weiner
2020-04-29 14:03 ` Johannes Weiner
2020-04-29 14:17 ` Yafang Shao
2020-04-29 14:27 ` Johannes Weiner
2020-04-29 14:31 ` Yafang Shao
2020-04-29 15:04 ` Michal Hocko
2020-04-29 16:56 ` Johannes Weiner
2020-04-30 14:57 ` Michal Hocko
2020-04-30 17:17 ` Roman Gushchin
2020-04-30 23:59 ` Yafang Shao
2020-05-04 7:23 ` Michal Hocko
2020-05-04 22:59 ` Roman Gushchin
2020-04-30 1:04 ` Yafang Shao
2020-04-30 1:16 ` Chris Down
2020-04-30 1:31 ` Yafang Shao
2020-04-30 1:46 ` Chris Down
2020-04-30 1:49 ` Yafang Shao
2020-04-28 18:27 ` [PATCH 2/2] mm, memcg: Decouple e{low,min} state mutations from protection checks Chris Down
2020-04-28 21:19 ` Johannes Weiner
2020-04-29 10:06 ` Michal Hocko
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.1588092152.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 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).