From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: sashiko-bot@kernel.org, Johannes Weiner <hannes@cmpxchg.org>,
Gregory Price <gourry@gourry.net>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <brendan.jackman@linux.dev>,
Zi Yan <ziy@nvidia.com>, Kairui Song <kasong@tencent.com>,
Qi Zheng <qi.zheng@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Barry Song <baohua@kernel.org>,
Axel Rasmussen <axelrasmussen@google.com>,
Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
Baoquan He <baoquan.he@linux.dev>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
linux-mm@kvack.org, kernel-team@meta.com
Subject: Re: [PATCH 2/2] mm/page_alloc: only skip kswapd nodes below their kswapd watermark
Date: Mon, 9 Nov 2026 17:38:33 +0000 [thread overview]
Message-ID: <avIFBnXPB2DLLjr6@gremlin> (raw)
In-Reply-To: <20261109172742.774437-1-joshua.hahnjy@gmail.com>
On Mon, Nov 09, 2026 at 09:27:36AM -0800, Joshua Hahn wrote:
> So initially I did not think this patch did not deserve a Fixes tag
> since it doesn't really fix a correctness issue, it's just adjusting
> a heuristic thatthe page allocator uses.
>
> But thinking about it over the weekend I think this might be worthy of
> a Fixes tag and a CC: stable since it just completely strands memory
> left unused on one NUMA node, which is an unintended consequence of the
> original fix that was proposed.
>
> Lorenzo, if it is OK with you I will opt to send this as a standalone
> fix, and then send the other fixes as a follow-up to make it look
> cleaner (like hoisting this check out into its own helper, and the other
> neighboring cleanups that I found). That way I won't have the cleanup
> patches blocking the fix from getting merged and it will be easier to
> backport in the future.
Ack, sounds reasonable!
>
> Thanks, Sashiko!
:)
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-11-09 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:26 [PATCH 1/2] mm/vmscan: consolidate promo vs. high watermark checks Joshua Hahn
2026-11-06 17:26 ` [PATCH 2/2] mm/page_alloc: only skip kswapd nodes below their kswapd watermark Joshua Hahn
2026-11-06 17:50 ` Lorenzo Stoakes (ARM)
2026-11-06 18:35 ` Joshua Hahn
2026-11-07 17:26 ` sashiko-bot
2026-11-09 17:27 ` Joshua Hahn
2026-11-09 17:38 ` Lorenzo Stoakes (ARM) [this message]
2026-11-06 17:42 ` [PATCH 1/2] mm/vmscan: consolidate promo vs. high watermark checks Lorenzo Stoakes (ARM)
2026-11-06 17:50 ` Joshua Hahn
2026-11-07 17:26 ` sashiko-bot
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=avIFBnXPB2DLLjr6@gremlin \
--to=ljs@kernel.org \
--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=brendan.jackman@linux.dev \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=joshua.hahnjy@gmail.com \
--cc=kasong@tencent.com \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=qi.zheng@linux.dev \
--cc=rppt@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.