From: Andrew Morton <akpm@linux-foundation.org>
To: mawupeng <mawupeng1@huawei.com>
Cc: <liuye@kylinos.cn>, <hannes@cmpxchg.org>, <mhocko@kernel.org>,
<david@kernel.org>, <ljs@kernel.org>, <hughd@google.com>,
<mgorman@techsingularity.net>, <yang@os.amperecomputing.com>,
<zhangqiuhao@huawei.com>, <wangkefeng.wang@huawei.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] mm: vmscan: fix scan overshoot and ineligible folio scanning
Date: Sat, 29 Aug 2026 20:18:09 -0700 [thread overview]
Message-ID: <20260829201809.99fe79c4725413bf80510fed@linux-foundation.org> (raw)
In-Reply-To: <f53b5d3a-9f16-460c-a7d7-a0f518c2f21d@huawei.com>
On Tue, 25 Aug 2026 08:59:54 +0800 mawupeng <mawupeng1@huawei.com> wrote:
> Hi, maintainers
> Kindly ping.
It's been quite a while. It would be helpful to refresh/retest/resend,
please.
While doing this, please update the changelogging to help reviewers
understand the end-user impact of the issue.
Please also give some though to whether we should backport these fixes
into earlier kernels, with a cc:stable. Given the unusual
circumstances which are required to hit this, I'm thinking "no", but
feel free to disagree!
prev parent reply other threads:[~2026-08-30 3:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 7:08 Wupeng Ma
2026-08-11 7:08 ` [PATCH 1/2] mm: vmscan: charge isolate overshoot against scan quota Wupeng Ma
2026-08-11 7:08 ` [PATCH 2/2] mm: vmscan: stop scanning ineligible folios after max_nr_skipped Wupeng Ma
2026-08-12 1:42 ` [PATCH 0/2] mm: vmscan: fix scan overshoot and ineligible folio scanning Andrew Morton
2026-08-12 2:29 ` mawupeng
2026-08-25 0:59 ` mawupeng
2026-08-30 3:18 ` Andrew Morton [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=20260829201809.99fe79c4725413bf80510fed@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=ljs@kernel.org \
--cc=mawupeng1@huawei.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=yang@os.amperecomputing.com \
--cc=zhangqiuhao@huawei.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®