From: Xueyuan Chen <xueyuan.chen21@gmail.com>
To: gourry@gourry.net
Cc: akpm@linux-foundation.org, axelrasmussen@google.com,
baohua@kernel.org, baolin.wang@linux.alibaba.com,
baoquan.he@linux.dev, dave@stgolabs.net, david@kernel.org,
hannes@cmpxchg.org, kasong@tencent.com, kernel-team@meta.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org,
mhocko@kernel.org, qi.zheng@linux.dev, roman.gushchin@linux.dev,
shakeel.butt@linux.dev, stable@vger.kernel.org,
weixugc@google.com, yuanchu@google.com
Subject: Re: [PATCH] mm/vmscan: reclaim every zone in per-node proactive reclaim
Date: Wed, 21 Oct 2026 20:27:56 +0800 [thread overview]
Message-ID: <179258562954.2.15216681747698947501.node-proactive-reclaim-review@gmail.com> (raw)
In-Reply-To: <20261019185002.3428594-1-gourry@gourry.net>
Including all zones makes sense here, since per-node proactive reclaim
is not serving an allocation. The existing GFP context restrictions
and folio isolation checks remain in place.
Reviewed-by: Xueyuan Chen <xueyuan.chen21@gmail.com>
next prev parent reply other threads:[~2026-10-21 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 18:50 Gregory Price (Meta)
2026-10-19 20:14 ` Barry Song
2026-10-19 20:16 ` Johannes Weiner
2026-10-19 20:51 ` Harry Yoo
2026-10-19 22:06 ` Shakeel Butt
2026-10-19 22:52 ` Yosry Ahmed
2026-10-20 0:36 ` SJ Park
2026-10-20 1:49 ` Balbir Singh
2026-10-20 3:04 ` Gregory Price
2026-10-20 7:49 ` Michal Hocko
2026-10-20 19:58 ` Gregory Price (Meta)
2026-10-20 20:35 ` Michal Hocko
2026-10-20 15:19 ` Kunwu Chan
2026-10-20 16:59 ` Davidlohr Bueso
2026-10-21 12:27 ` Xueyuan Chen [this message]
2026-10-21 12:31 ` Lorenzo Stoakes (ARM)
2026-10-21 13:42 ` Gregory Price
2026-10-21 14:02 ` Vishal Moola (Fractile)
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=179258562954.2.15216681747698947501.node-proactive-reclaim-review@gmail.com \
--to=xueyuan.chen21@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baoquan.he@linux.dev \
--cc=dave@stgolabs.net \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=qi.zheng@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 \
/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
all inboxes | Powered by JetHome®