From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jiayuan Chen <jiayuan.chen@linux.dev>,
linux-mm@kvack.org, Jiayuan Chen <jiayuan.chen@shopee.com>,
Johannes Weiner <hannes@cmpxchg.org>,
David Hildenbrand <david@kernel.org>,
Michal Hocko <mhocko@kernel.org>,
Qi Zheng <zhengqi.arch@bytedance.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/vmscan: mitigate spurious kswapd_failures reset from direct reclaim
Date: Mon, 29 Dec 2025 20:10:39 -0800 [thread overview]
Message-ID: <hgknetkzqpunmtj2ui7kednwrrc6gu4z6ooxgfzoogqijdxxqe@njfmrkrwpkg2> (raw)
In-Reply-To: <20251228114622.9a8534ede47866c42322b0b3@linux-foundation.org>
On Sun, Dec 28, 2025 at 11:46:22AM -0800, Andrew Morton wrote:
> On Fri, 26 Dec 2025 16:00:42 +0800 Jiayuan Chen <jiayuan.chen@linux.dev> wrote:
>
> > This is v2 of this patch series. For v1, see [1].
>
> This isn't significantly different from v1. You appear to be
> mid-discussion with Shakeel on v1.
Yes, the discussion will continue.
Jiayuan, please don't send a new version until the discussion is
concluded. If there is slow response, just ping on the same email chain.
I will respond on v1 to keep the context of the discussion at the same
place.
prev parent reply other threads:[~2025-12-30 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251226080042.291657-1-jiayuan.chen@linux.dev>
2025-12-28 19:46 ` Andrew Morton
2025-12-30 4:10 ` Shakeel Butt [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=hgknetkzqpunmtj2ui7kednwrrc6gu4z6ooxgfzoogqijdxxqe@njfmrkrwpkg2 \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jiayuan.chen@linux.dev \
--cc=jiayuan.chen@shopee.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--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