All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qi Zheng <qi.zheng@linux.dev>
To: Ridong Chen <ridong.chen@linux.dev>, akpm@linux-foundation.org
Cc: hannes@cmpxchg.org, david@kernel.org, mhocko@kernel.org,
	shakeel.butt@linux.dev, ljs@kernel.org, kasong@tencent.com,
	baohua@kernel.org, axelrasmussen@google.com, yuanchu@google.com,
	weixugc@google.com, hezhongkun.hzk@bytedance.com,
	muchun.song@linux.dev, dave@stgolabs.net,
	roman.gushchin@linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, Ridong Chen <chenridong@xiaomi.com>
Subject: Re: [PATCH v2 1/4] mm/vmscan: fix anon-only reclaim evicting file pages when swappiness=max
Date: Mon, 20 Jul 2026 10:27:43 +0800	[thread overview]
Message-ID: <bb41fe18-71a0-4574-9941-fb30e48bf4c3@linux.dev> (raw)
In-Reply-To: <20260718095251.82937-2-ridong.chen@linux.dev>



On 7/18/26 5:52 PM, Ridong Chen wrote:
> From: Ridong Chen <chenridong@xiaomi.com>
> 
> As Qi mentioned [1], when swappiness=max (SWAPPINESS_ANON_ONLY) is set,
> the reclaim logic is expected to reclaim anonymous pages exclusively.
> However, due to the current ordering of checks in get_scan_count(),
> file pages may still be evicted if can_reclaim_anon_pages() returns
> false, which contradicts the semantics of SWAPPINESS_ANON_ONLY.
> 
> Reproducer in a cgroup holding 64M of file cache, with no swap configured:
> 
>    Before (file cache is wrongly evicted):
>      # cat memory.stat
>      anon 196608
>      file 67178496
>      pgscan_proactive 0
>      # echo "64M swappiness=max" > memory.reclaim
>      # cat memory.stat
>      anon 208896
>      file 4096                 <- page cache evicted
>      pgsteal_proactive 16400
>      pgscan_proactive 16400
> 
>    After (file cache is left intact):
>      # cat memory.stat
>      anon 200704
>      file 67178496
>      pgscan_proactive 0
>      # echo "64M swappiness=max" > memory.reclaim
>      -bash: echo: write error: Resource temporarily unavailable
>      # cat memory.stat
>      anon 208896
>      file 67178496             <- page cache untouched
>      pgsteal_proactive 0
>      pgscan_proactive 0
> 
> Fix this by bailing out early when SWAPPINESS_ANON_ONLY is set and no
> anonymous pages are reclaimable, before falling back to file reclaim.
> 
> [1] https://lore.kernel.org/cgroups/7ddf3eee-5fe2-45f7-8614-c8936a039e04@linux.dev/
> 
> Fixes: 68a1436bde00 ("mm: add swappiness=max arg to memory.reclaim for only anon reclaim")
> Suggested-by: Qi Zheng <qi.zheng@linux.dev>
> Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
> Reviewed-by: Muchun Song <muchun.song@linux.dev>
> Signed-off-by: Ridong Chen <chenridong@xiaomi.com>
> ---
>   mm/vmscan.c | 18 +++++++++++-------
>   1 file changed, 11 insertions(+), 7 deletions(-)

Thanks for the fix!

Reviewed-by: Qi Zheng <qi.zheng@linux.dev>

> 
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 35c3bb15ae96..d6b383d96a0c 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -2501,6 +2501,17 @@ static void get_scan_count(struct lruvec *lruvec, struct scan_control *sc,
>   	enum scan_balance scan_balance;
>   	enum lru_list lru;
>   
> +	/* Proactive reclaim initiated by userspace for anonymous memory only */
> +	if (swappiness == SWAPPINESS_ANON_ONLY) {
> +		WARN_ON_ONCE(!sc->proactive);
> +		if (!can_reclaim_anon_pages(memcg, pgdat->node_id, sc)) {
> +			memset(nr, 0, sizeof(*nr) * NR_LRU_LISTS);
> +			return;
> +		}
> +		scan_balance = SCAN_ANON;
> +		goto out;
> +	}
> +
>   	/* If we have no swap space, do not bother scanning anon folios. */
>   	if (!sc->may_swap || !can_reclaim_anon_pages(memcg, pgdat->node_id, sc)) {
>   		scan_balance = SCAN_FILE;
> @@ -2519,13 +2530,6 @@ static void get_scan_count(struct lruvec *lruvec, struct scan_control *sc,
>   		goto out;
>   	}
>   
> -	/* Proactive reclaim initiated by userspace for anonymous memory only */
> -	if (swappiness == SWAPPINESS_ANON_ONLY) {
> -		WARN_ON_ONCE(!sc->proactive);
> -		scan_balance = SCAN_ANON;
> -		goto out;
> -	}
> -
>   	/*
>   	 * Do not apply any pressure balancing cleverness when the
>   	 * system is close to OOM, scan both anon and file equally



  parent reply	other threads:[~2026-07-20  2:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18  9:52 [PATCH v2 0/4] mm/vmscan: fix swappiness=max and clean up per-node proactive reclaim Ridong Chen
2026-07-18  9:52 ` [PATCH v2 1/4] mm/vmscan: fix anon-only reclaim evicting file pages when swappiness=max Ridong Chen
2026-07-18 13:34   ` Barry Song
2026-07-20  4:42     ` Ridong Chen
2026-07-21  7:45       ` Barry Song
2026-07-20  2:27   ` Qi Zheng [this message]
2026-07-18  9:52 ` [PATCH v2 2/4] mm: vmscan: propagate real error code from per-node proactive reclaim Ridong Chen
2026-07-20  2:32   ` Qi Zheng
2026-07-21  7:32   ` Barry Song
2026-07-18  9:52 ` [PATCH v2 3/4] mm: vmscan: drop unused gfp_mask parameter from __node_reclaim() Ridong Chen
2026-07-18 13:12   ` Barry Song
2026-07-20  2:34   ` Qi Zheng
2026-07-18  9:52 ` [PATCH v2 4/4] mm/mglru: fix anon-only reclaim evicting file pages when swappiness=max Ridong Chen
2026-07-18 13:43   ` Barry Song
2026-07-20  2:48     ` Qi Zheng
2026-07-20  6:03       ` Ridong Chen

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=bb41fe18-71a0-4574-9941-fb30e48bf4c3@linux.dev \
    --to=qi.zheng@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=baohua@kernel.org \
    --cc=chenridong@xiaomi.com \
    --cc=dave@stgolabs.net \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=hezhongkun.hzk@bytedance.com \
    --cc=kasong@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=ridong.chen@linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=weixugc@google.com \
    --cc=yuanchu@google.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.