From: Tim Chen <tim.c.chen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>,
Vladimir Davydov
<vdavydov.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Tim Chen <tim.c.chen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Dave Hansen <dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Ying Huang <ying.huang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2 0/3] Soft limit memory management bug fixes
Date: Wed, 17 Feb 2021 12:41:33 -0800 [thread overview]
Message-ID: <cover.1613584277.git.tim.c.chen@linux.intel.com> (raw)
During testing of tiered memory management based on memory soft limit,
I found three issues with memory management using cgroup based soft
limit in the mainline code. Fix the issues with the three patches in
this series. Also updated patch 3 per Johannes' comments on the first
version of this patch.
Thanks.
Tim
Changelog:
v2
1. Do soft limit tree uncharge update in batch of the same node only
for v1 cgroups that have a soft limit. Batching in nodes is only
relevant for cgroup v1 that has per node soft limit tree.
Tim Chen (3):
mm: Fix dropped memcg from mem cgroup soft limit tree
mm: Force update of mem cgroup soft limit tree on usage excess
mm: Fix missing mem cgroup soft limit tree updates
mm/memcontrol.c | 27 +++++++++++++++++++++++----
1 file changed, 23 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2021-02-17 20:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 20:41 Tim Chen [this message]
2021-02-17 20:41 ` [PATCH v2 1/3] mm: Fix dropped memcg from mem cgroup soft limit tree Tim Chen
[not found] ` <8d35206601ccf0e1fe021d24405b2a0c2f4e052f.1613584277.git.tim.c.chen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-02-18 8:24 ` Michal Hocko
[not found] ` <YC4kV7dkJpxjW+df-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-02-18 18:30 ` Tim Chen
[not found] ` <c3ffa2cb-cb2c-20b7-d722-c875934992e9-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-02-18 19:13 ` Michal Hocko
[not found] ` <YC68QRVsCONXscCl-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-02-18 19:51 ` Tim Chen
2021-02-18 19:13 ` Michal Hocko
[not found] ` <YC68Xo9+R2msn/ul-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-03-04 17:35 ` Tim Chen
[not found] ` <72cb8618-73af-ce08-d5d5-30cab30755a3-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-03-05 9:11 ` Michal Hocko
[not found] ` <YEH1xF8xm9MCsQ+q-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-03-05 19:07 ` Tim Chen
2021-03-08 8:34 ` Michal Hocko
2021-02-17 20:41 ` [PATCH v2 2/3] mm: Force update of mem cgroup soft limit tree on usage excess Tim Chen
[not found] ` <06f1f92f1f7d4e57c4e20c97f435252c16c60a27.1613584277.git.tim.c.chen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-02-19 9:11 ` Michal Hocko
[not found] ` <YC+ApsntwnlVfCuK-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-02-19 18:59 ` Tim Chen
[not found] ` <884d7559-e118-3773-351d-84c02642ca96-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-02-20 16:23 ` Tim Chen
2021-02-22 8:40 ` Michal Hocko
[not found] ` <YDNuAIztiGJpLEtw-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-02-22 17:41 ` Tim Chen
[not found] ` <e132f836-b5d5-3776-22d6-669e713983e4-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-02-22 19:09 ` Michal Hocko
[not found] ` <YDQBh5th9txxEFUm-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-02-22 19:23 ` Tim Chen
2021-02-22 19:48 ` Tim Chen
[not found] ` <cf5ca7a1-7965-f307-22e1-e216316904cf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-02-24 11:53 ` Michal Hocko
[not found] ` <YDY+PydRUGQpHNaJ-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-02-25 22:48 ` Tim Chen
2021-02-26 8:52 ` Michal Hocko
[not found] ` <YDi2udQqIML6Vdpo-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-02-27 0:56 ` Tim Chen
[not found] ` <781634ee-ffb9-598d-fdb6-0ae6067448b7-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-03-01 7:39 ` Michal Hocko
2021-02-25 22:25 ` Tim Chen
2021-03-02 6:25 ` [mm] 4f09feb8bf: vm-scalability.throughput -4.3% regression kernel test robot
[not found] ` <cover.1613584277.git.tim.c.chen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-02-17 20:41 ` [PATCH v2 3/3] mm: Fix missing mem cgroup soft limit tree updates Tim Chen
[not found] ` <e269f5df3af1157232b01a9b0dae3edf4880d786.1613584277.git.tim.c.chen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-02-18 5:56 ` Johannes Weiner
[not found] ` <YC4BcsNFEmW7XeqB-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2021-02-22 18:38 ` Tim Chen
2021-02-23 15:18 ` Johannes Weiner
2021-02-19 9:16 ` Michal Hocko
2021-02-19 19:28 ` Tim Chen
[not found] ` <1ecd277e-c236-08e1-f068-3dd65ee0e640-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2021-02-22 8:41 ` Michal Hocko
[not found] ` <YDNuRFgJPH4bPEbq-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-02-22 17:45 ` Tim Chen
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.1613584277.git.tim.c.chen@linux.intel.com \
--to=tim.c.chen-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=vdavydov.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ying.huang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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).