Re: [PATCH v3 0/4] mm/vmscan: fix swappiness=max and clean up per-node proactive reclaim

[Ridong Chen]

On 7/24/2026 8:18 AM, Andrew Morton wrote:
> On Thu, 23 Jul 2026 12:57:14 +0800 Ridong <ridong.chen@xxxxxxxxx> wrote:
>
> > Fixes and one cleanup.
> >
> > Patch 1 fixes "swappiness=max": the anon-only test in get_scan_count()
> > sat after the "cannot reclaim anon" check, so when no anon was
> > reclaimable the request fell back to SCAN_FILE and evicted page cache
> > instead.
> >
> > Patch 2 fixes reclaim_store() collapsing every error into -EAGAIN, so
> > callers can no longer tell an invalid argument from a busy interface;
> > propagate the real error code, matching the memcg path.
> >
> > Patch 3 drops the now-unused gfp_mask parameter from __node_reclaim().
> >
> > Patch 4 fixes the same "swappiness=max" issue for MGLRU.
>
> Thanks.  AI review might have found several pre-existing issues which
> might interest the maintainers.  Also a suggestion against your [4/4]:
>
> 	https://sashiko.dev/#/patchset/20260723045718.2052070-1-ridong.chen@xxxxxxxxx


Thanks. I will update patch 4/4 as suggested.

--
Best regards
Ridong