linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chengming Zhou <chengming.zhou@linux.dev>
To: Takero Funaki <flintglass@gmail.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Yosry Ahmed <yosryahmed@google.com>,
	Nhat Pham <nphamcs@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] mm: zswap: fix global shrinker error handling logic
Date: Thu, 1 Aug 2024 15:40:16 +0800	[thread overview]
Message-ID: <1f6b254f-9cb9-412e-b249-8efe1d4157d3@linux.dev> (raw)
In-Reply-To: <20240731004918.33182-3-flintglass@gmail.com>

On 2024/7/31 08:49, Takero Funaki wrote:
> This patch fixes the zswap global shrinker, which did not shrink the
> zpool as expected.
> 
> The issue addressed is that shrink_worker() did not distinguish between
> unexpected errors and expected errors, such as failed writeback from an
> empty memcg. The shrinker would stop shrinking after iterating through
> the memcg tree 16 times, even if there was only one empty memcg.
> 
> With this patch, the shrinker no longer considers encountering an empty
> memcg, encountering a memcg with writeback disabled, or reaching the end
> of a memcg tree walk as a failure, as long as there are memcgs that are
> candidates for writeback. Systems with one or more empty memcgs will now
> observe significantly higher zswap writeback activity after the zswap
> pool limit is hit.
> 
> To avoid an infinite loop when there are no writeback candidates, this
> patch tracks writeback attempts during memcg tree walks and limits
> reties if no writeback candidates are found.
> 
> To handle the empty memcg case, the helper function shrink_memcg() is
> modified to check if the memcg is empty and then return -ENOENT.
> 
> Fixes: a65b0e7607cc ("zswap: make shrinking memcg-aware")
> Signed-off-by: Takero Funaki <flintglass@gmail.com>

Looks good to me:

Reviewed-by: Chengming Zhou <chengming.zhou@linux.dev>

Thanks.

> ---
>   mm/zswap.c | 40 +++++++++++++++++++++++++++++++++-------
>   1 file changed, 33 insertions(+), 7 deletions(-)
> 
> diff --git a/mm/zswap.c b/mm/zswap.c
> index 3c16a1192252..d46caa42ed4f 100644
> --- a/mm/zswap.c
> +++ b/mm/zswap.c
> @@ -1287,10 +1287,10 @@ static struct shrinker *zswap_alloc_shrinker(void)
>   
>   static int shrink_memcg(struct mem_cgroup *memcg)
>   {
> -	int nid, shrunk = 0;
> +	int nid, shrunk = 0, scanned = 0;
>   
>   	if (!mem_cgroup_zswap_writeback_enabled(memcg))
> -		return -EINVAL;
> +		return -ENOENT;
>   
>   	/*
>   	 * Skip zombies because their LRUs are reparented and we would be
> @@ -1304,21 +1304,34 @@ static int shrink_memcg(struct mem_cgroup *memcg)
>   
>   		shrunk += list_lru_walk_one(&zswap_list_lru, nid, memcg,
>   					    &shrink_memcg_cb, NULL, &nr_to_walk);
> +		scanned += 1 - nr_to_walk;
>   	}
> +
> +	if (!scanned)
> +		return -ENOENT;
> +
>   	return shrunk ? 0 : -EAGAIN;
>   }
>   
>   static void shrink_worker(struct work_struct *w)
>   {
>   	struct mem_cgroup *memcg;
> -	int ret, failures = 0;
> +	int ret, failures = 0, attempts = 0;
>   	unsigned long thr;
>   
>   	/* Reclaim down to the accept threshold */
>   	thr = zswap_accept_thr_pages();
>   
>   	/*
> -	 * Global reclaim will select cgroup in a round-robin fashion.
> +	 * Global reclaim will select cgroup in a round-robin fashion from all
> +	 * online memcgs, but memcgs that have no pages in zswap and
> +	 * writeback-disabled memcgs (memory.zswap.writeback=0) are not
> +	 * candidates for shrinking.
> +	 *
> +	 * Shrinking will be aborted if we encounter the following
> +	 * MAX_RECLAIM_RETRIES times:
> +	 * - No writeback-candidate memcgs found in a memcg tree walk.
> +	 * - Shrinking a writeback-candidate memcg failed.
>   	 *
>   	 * We save iteration cursor memcg into zswap_next_shrink,
>   	 * which can be modified by the offline memcg cleaner
> @@ -1356,9 +1369,14 @@ static void shrink_worker(struct work_struct *w)
>   		spin_unlock(&zswap_shrink_lock);
>   
>   		if (!memcg) {
> -			if (++failures == MAX_RECLAIM_RETRIES)
> +			/*
> +			 * Continue shrinking without incrementing failures if
> +			 * we found candidate memcgs in the last tree walk.
> +			 */
> +			if (!attempts && ++failures == MAX_RECLAIM_RETRIES)
>   				break;
>   
> +			attempts = 0;
>   			goto resched;
>   		}
>   
> @@ -1366,8 +1384,16 @@ static void shrink_worker(struct work_struct *w)
>   		/* drop the extra reference */
>   		mem_cgroup_put(memcg);
>   
> -		if (ret == -EINVAL)
> -			break;
> +		/*
> +		 * There are no writeback-candidate pages in the memcg.
> +		 * This is not an issue as long as we can find another memcg
> +		 * with pages in zswap. Skip this without incrementing attempts
> +		 * and failures.
> +		 */
> +		if (ret == -ENOENT)
> +			continue;
> +		++attempts;
> +
>   		if (ret && ++failures == MAX_RECLAIM_RETRIES)
>   			break;
>   resched:


  reply	other threads:[~2024-08-01  7:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31  0:49 [PATCH v5 0/2] mm: zswap: fixes for global shrinker Takero Funaki
2024-07-31  0:49 ` [PATCH v5 1/2] mm: zswap: fix global shrinker memcg iteration Takero Funaki
2024-08-03  4:14   ` Yosry Ahmed
2024-07-31  0:49 ` [PATCH v5 2/2] mm: zswap: fix global shrinker error handling logic Takero Funaki
2024-08-01  7:40   ` Chengming Zhou [this message]
2024-08-02 22:51   ` Nhat Pham

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=1f6b254f-9cb9-412e-b249-8efe1d4157d3@linux.dev \
    --to=chengming.zhou@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=flintglass@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=yosryahmed@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).