From: Andrew Morton <akpm@linux-foundation.org>
To: Petr Tesarik <ptesarik@suse.com>
Cc: David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] mm: let node_reclaim() return the number of pages reclaimed
Date: Fri, 10 Jul 2026 16:27:29 -0700 [thread overview]
Message-ID: <20260710162729.b340eac3c83d4c3e0369558b@linux-foundation.org> (raw)
In-Reply-To: <20260710152320.2024283-1-ptesarik@suse.com>
On Fri, 10 Jul 2026 17:23:20 +0200 Petr Tesarik <ptesarik@suse.com> wrote:
> There is only one caller, get_page_from_freelist(), and it does not make
> any use of the reason for skipping the reclaim, nor does it make any
> distinction between a full and partially successful reclaim.
>
> Therefore, node_reclaim() can simply return the number of pages that have
> been reclaimed, same as __node_reclaim(), and the NODE_RECLAIM_xxx macros
> can be removed.
AI review
(https://sashiko.dev/#/patchset/20260710152320.2024283-1-ptesarik@suse.com)
points out that the macros weren't actually removed. Perhaps you meant
"use of the macros can be removed" or similar. But it does seem they
can indeed be removed:
hp2:/usr/src/25> grep NODE_RECLAIM_ mm/*.[ch] include/linux/*.h
mm/internal.h:#define NODE_RECLAIM_NOSCAN -2
mm/internal.h:#define NODE_RECLAIM_FULL -1
mm/internal.h:#define NODE_RECLAIM_SOME 0
mm/internal.h:#define NODE_RECLAIM_SUCCESS 1
mm/vmscan.c:#define NODE_RECLAIM_PRIORITY 4
mm/vmscan.c: .priority = NODE_RECLAIM_PRIORITY,
(NODE_RECLAIM_PRIORITY looks like it belongs, but it's an unrelated
thing).
Let's not do an immediate resend to address this please - let's give
reviewers a week or so to do their thing.
prev parent reply other threads:[~2026-07-10 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 15:23 [PATCH v3 1/1] mm: let node_reclaim() return the number of pages reclaimed Petr Tesarik
2026-07-10 23:27 ` 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=20260710162729.b340eac3c83d4c3e0369558b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=ptesarik@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox