From: Johannes Weiner <hannes@cmpxchg.org>
To: Ridong Chen <ridong.chen@linux.dev>
Cc: Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Muchun Song <muchun.song@linux.dev>,
David Hildenbrand <david@kernel.org>,
Qi Zheng <qi.zheng@linux.dev>, Lorenzo Stoakes <ljs@kernel.org>,
Kairui Song <kasong@tencent.com>, Barry Song <baohua@kernel.org>,
Axel Rasmussen <axelrasmussen@google.com>,
Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
Yu Zhao <yuzhao@google.com>,
"open list:CONTROL GROUP - MEMORY RESOURCE CONTROLLER (MEMCG)"
<cgroups@vger.kernel.org>,
"open list:CONTROL GROUP - MEMORY RESOURCE CONTROLLER (MEMCG)"
<linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, Ridong Chen <chenridong@xiaomi.com>,
stable@vger.kernel.org
Subject: Re: [RFC PATCH] mm/mglru: fix ineffective memory protection for non-kswapd reclaim
Date: Thu, 27 Aug 2026 13:21:41 -0400 [thread overview]
Message-ID: <20260827172141.GF3004@cmpxchg.org> (raw)
In-Reply-To: <20260826133054.88529-1-ridong.chen@linux.dev>
On Wed, Aug 26, 2026 at 09:30:54PM +0800, Ridong Chen wrote:
> From: Ridong Chen <chenridong@xiaomi.com>
>
> memory.min/low is silently bypassed for MGLRU during global proactive
> reclaim (writing to the root memory.reclaim) and global direct reclaim.
> It can be reproduced as follows:
>
> # echo 7 > /sys/kernel/mm/lru_gen/enabled
> # cd /sys/fs/cgroup
> # mkdir -p a/b
> # echo 100M > a/memory.min
> # echo +memory > a/cgroup.subtree_control
> # echo 100M > a/b/memory.min
> # echo $$ > a/b/cgroup.procs
> # dd if=/dev/zero of=/tmp/testfile bs=1M count=200
> # cat a/b/memory.current
> 222650368
> # echo 500M > memory.reclaim
> -bash: echo: write error: Resource temporarily unavailable
> # cat a/b/memory.current
> 6070272
>
> memory.min is 100M, yet reclaim drops a/b down to 6M, breaking the
> protection. The traditional LRU path is not affected because
> shrink_node() calls mem_cgroup_calculate_protection() for each memcg it
> visits during a top-down tree walk.
>
> Commit 30d77b7eef01 ("mm/mglru: fix ineffective protection calculation")
> moved the protection computation into lru_gen_age_node(), which only
> runs for kswapd. Non-kswapd global reclaim reaches shrink_one() through
> lru_gen_shrink_node() -> shrink_many() without any protection
> computation, so emin/elow remain stale or zero.
>
> Introduce mem_cgroup_protection_path() which computes emin/elow along
> the root-to-target path only by iterating through the cgroup ancestors
> array top-down. This avoids the full tree traversal that would be
> needed with mem_cgroup_calculate_protection(), limiting the cost to
> O(depth) per memcg - typically 3-5 levels.
Right, because of the memcg-lru...
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -5198,6 +5198,48 @@ void mem_cgroup_calculate_protection(struct mem_cgroup *root,
> page_counter_calculate_protection(&root->memory, &memcg->memory, recursive_protection);
> }
>
> +/**
> + * mem_cgroup_protection_path - compute protection along root->memcg path
> + * @root: the top ancestor of the sub-tree being checked (NULL for root_mem_cgroup)
> + * @memcg: the target memory cgroup
> + *
> + * Walk the ancestor path from @root down to @memcg and compute the effective
> + * protection at each level. This is safe for isolated queries because it
> + * ensures parents are computed before children.
> + */
> +void mem_cgroup_protection_path(struct mem_cgroup *root,
> + struct mem_cgroup *memcg)
> +{
> + bool recursive_protection =
> + cgrp_dfl_root.flags & CGRP_ROOT_MEMORY_RECURSIVE_PROT;
> + struct cgroup *cg;
> + int root_level, i;
> +
> + if (mem_cgroup_disabled())
> + return;
> +
> + if (!root)
> + root = root_mem_cgroup;
> +
> + if (memcg == root)
> + return;
> +
> + root_level = root->css.cgroup->level;
> + cg = memcg->css.cgroup;
> +
> + rcu_read_lock();
> + for (i = root_level + 1; i <= cg->level; i++) {
> + struct mem_cgroup *cur;
> +
> + cur = mem_cgroup_from_css(cgroup_css(cg->ancestors[i],
> + &memory_cgrp_subsys));
> + if (cur)
> + page_counter_calculate_protection(&root->memory,
> + &cur->memory, recursive_protection);
> + }
> + rcu_read_unlock();
> +}
Please wrap this in a #ifdef CONFIG_LRU_GEN block.
next prev parent reply other threads:[~2026-08-27 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 13:30 [RFC PATCH] mm/mglru: fix ineffective memory protection for non-kswapd reclaim Ridong Chen
2026-08-27 1:37 ` Ridong Chen
[not found] ` <20260826134733.051941F000E9@smtp.kernel.org>
[not found] ` <0c606cf9-2b5a-4549-8ab1-0be619487412@linux.dev>
2026-08-27 9:26 ` Michal Koutný
2026-08-28 1:49 ` Ridong Chen
2026-08-27 17:21 ` Johannes Weiner [this message]
2026-08-28 1:51 ` Ridong 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=20260827172141.GF3004@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@xiaomi.com \
--cc=david@kernel.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=qi.zheng@linux.dev \
--cc=ridong.chen@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=yuzhao@google.com \
/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.