From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Barry Song <21cnbao@gmail.com>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, david@kernel.org,
mhocko@kernel.org, zhengqi.arch@bytedance.com,
shakeel.butt@linux.dev, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, kasong@tencent.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] mm: vmscan: fix dirty folios throttling on cgroup v1 for MGLRU
Date: Thu, 26 Mar 2026 16:41:25 +0800 [thread overview]
Message-ID: <b6f8e48d-4440-44ac-b4c9-79aa777ad2da@linux.alibaba.com> (raw)
In-Reply-To: <CAGsJ_4x4-hURgpH4ctpUG41bpeyrMYWrVNvyZLYheunNqrgY1Q@mail.gmail.com>
On 3/26/26 1:04 PM, Barry Song wrote:
> On Wed, Mar 25, 2026 at 7:51 PM Baolin Wang
> <baolin.wang@linux.alibaba.com> wrote:
>>
>> The balance_dirty_pages() won't do the dirty folios throttling on cgroupv1.
>> See commit 9badce000e2c ("cgroup, writeback: don't enable cgroup writeback
>> on traditional hierarchies").
>>
>> Moreover, after commit 6b0dfabb3555 ("fs: Remove aops->writepage"), we no
>> longer attempt to write back filesystem folios through reclaim.
>>
>> On large memory systems, the flusher may not be able to write back quickly
>> enough. Consequently, MGLRU will encounter many folios that are already
>> under writeback. Since we cannot reclaim these dirty folios, the system
>> may run out of memory and trigger the OOM killer.
>>
>> Hence, for cgroup v1, let's throttle reclaim after waking up the flusher,
>> which is similar to commit 81a70c21d917 ("mm/cgroup/reclaim: fix dirty
>> pages throttling on cgroup v1"), to avoid unnecessary OOM.
>>
>> The following test program can easily reproduce the OOM issue. With this patch
>> applied, the test passes successfully.
>>
>> $mkdir /sys/fs/cgroup/memory/test
>> $echo 256M > /sys/fs/cgroup/memory/test/memory.limit_in_bytes
>> $echo $$ > /sys/fs/cgroup/memory/test/cgroup.procs
>> $dd if=/dev/zero of=/mnt/data.bin bs=1M count=800
>>
>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>
> LGTM,
>
> Reviewed-by: Barry Song <baohua@kernel.org>
Thanks.
> Maybe we can extract a common inline helper to avoid the copy-paste duplication.
Kairui is planning further optimizations here (including using a helper)
[1], so it might be better to leave that for his series.
For this patch, I intend it to be a standalone fix, and I will add the
Fixes: ac35a4902374 ("mm: multi-gen LRU: minimal implementation") tag.
[1]
https://lore.kernel.org/all/20260318-mglru-reclaim-v1-7-2c46f9eb0508@tencent.com/
>> ---
>> mm/vmscan.c | 13 ++++++++++++-
>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index 33287ba4a500..a9648269fae8 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -5036,9 +5036,20 @@ static bool try_to_shrink_lruvec(struct lruvec *lruvec, struct scan_control *sc)
>> * If too many file cache in the coldest generation can't be evicted
>> * due to being dirty, wake up the flusher.
>> */
>> - if (sc->nr.unqueued_dirty && sc->nr.unqueued_dirty == sc->nr.file_taken)
>> + if (sc->nr.unqueued_dirty && sc->nr.unqueued_dirty == sc->nr.file_taken) {
>> + struct pglist_data *pgdat = lruvec_pgdat(lruvec);
>> +
>> wakeup_flusher_threads(WB_REASON_VMSCAN);
>>
>> + /*
>> + * For cgroupv1 dirty throttling is achieved by waking up
>> + * the kernel flusher here and later waiting on folios
>> + * which are in writeback to finish (see shrink_folio_list()).
>> + */
>> + if (!writeback_throttling_sane(sc))
>> + reclaim_throttle(pgdat, VMSCAN_THROTTLE_WRITEBACK);
>> + }
>> +
>> /* whether this lruvec should be rotated */
>> return nr_to_scan < 0;
>> }
>> --
>> 2.47.3
>>
prev parent reply other threads:[~2026-03-26 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 11:50 [RFC PATCH] mm: vmscan: fix dirty folios throttling on cgroup v1 for MGLRU Baolin Wang
2026-03-25 11:55 ` Baolin Wang
2026-03-25 12:07 ` Kairui Song
2026-03-25 13:20 ` Baolin Wang
2026-03-25 13:35 ` Kairui Song
2026-03-26 1:57 ` Baolin Wang
2026-03-26 5:04 ` Barry Song
2026-03-26 8:41 ` Baolin Wang [this message]
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=b6f8e48d-4440-44ac-b4c9-79aa777ad2da@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=zhengqi.arch@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox