[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aVtHRi-D3iSb3ZkQ@google.com>
Date: Mon, 5 Jan 2026 05:08:22 +0000
From: Bing Jiao <bingjiao@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org, gourry@...rry.net,
longman@...hat.com, hannes@...xchg.org, mhocko@...nel.org,
roman.gushchin@...ux.dev, shakeel.butt@...ux.dev,
muchun.song@...ux.dev, tj@...nel.org, mkoutny@...e.com,
david@...nel.org, zhengqi.arch@...edance.com,
lorenzo.stoakes@...cle.com, axelrasmussen@...gle.com,
chenridong@...weicloud.com, yuanchu@...gle.com, weixugc@...gle.com,
cgroups@...r.kernel.org, Akinobu Mita <akinobu.mita@...il.com>
Subject: Re: [PATCH v4] mm/vmscan: fix demotion targets checks in
reclaim/demotion
On Sun, Jan 04, 2026 at 10:27:45AM -0800, Andrew Morton wrote:
> We'll want to fix these things in 6.16.X and later, but you've prepared
> this patch against "mm/vmscan: don't demote if there is not enough free
> memory in the lower memory tier", which is presently under test/review
> in mm.git's mm-unstable branch.
>
> This seems to be incorrect ordering - this fix should go ahead of
> Akinobu Mita's series "mm: fix oom-killer not being invoked when
> demotion is enabled v2".
>
> So can you please redo this patch against current mainline? And please
> also review the "mm: fix oom-killer not being invoked when demotion is
> enabled" series to ensure that things will work together nicely when
> that time comes.
Hi Andrew,
Thank you for the detailed explanation. Patch v4 has been sent.
V4 is patched against the mainline. Tested on both the mainline and
mm-everything (after Akinobu Mita's series "mm: fix oom-killer not
being invoked when demotion is enabled v2"), and passed.
Best,
Bing
Powered by blists - more mailing lists