From: Chengming Zhou <chengming.zhou@linux.dev>
To: Yosry Ahmed <yosryahmed@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Nhat Pham <nphamcs@gmail.com>,
Takero Funaki <flintglass@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: zswap: make the lock critical section obvious in shrink_worker()
Date: Mon, 5 Aug 2024 10:06:33 +0800 [thread overview]
Message-ID: <a3fc7bc6-d9c0-43e2-a530-4dafff61203b@linux.dev> (raw)
In-Reply-To: <20240803053306.2685541-1-yosryahmed@google.com>
On 2024/8/3 13:33, Yosry Ahmed wrote:
> Move the comments and spin_{lock/unlock}() calls around in
> shrink_worker() to make it obvious the lock is protecting the loop
> updating zswap_next_shrink.
>
> Signed-off-by: Yosry Ahmed <yosryahmed@google.com>
Yeah, it's clearer.
Reviewed-by: Chengming Zhou <chengming.zhou@linux.dev>
Thanks.
> ---
>
> This is intended to be squashed into "mm: zswap: fix global shrinker
> memcg iteration".
>
> ---
> mm/zswap.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/mm/zswap.c b/mm/zswap.c
> index babf0abbcc765..df620eacd1d11 100644
> --- a/mm/zswap.c
> +++ b/mm/zswap.c
> @@ -1364,24 +1364,22 @@ static void shrink_worker(struct work_struct *w)
> * until the next run of shrink_worker().
> */
> do {
> - spin_lock(&zswap_shrink_lock);
> -
> /*
> * Start shrinking from the next memcg after zswap_next_shrink.
> * When the offline cleaner has already advanced the cursor,
> * advancing the cursor here overlooks one memcg, but this
> * should be negligibly rare.
> + *
> + * If we get an online memcg, keep the extra reference in case
> + * the original one obtained by mem_cgroup_iter() is dropped by
> + * zswap_memcg_offline_cleanup() while we are shrinking the
> + * memcg.
> */
> + spin_lock(&zswap_shrink_lock);
> do {
> memcg = mem_cgroup_iter(NULL, zswap_next_shrink, NULL);
> zswap_next_shrink = memcg;
> } while (memcg && !mem_cgroup_tryget_online(memcg));
> - /*
> - * Note that if we got an online memcg, we will keep the extra
> - * reference in case the original reference obtained by mem_cgroup_iter
> - * is dropped by the zswap memcg offlining callback, ensuring that the
> - * memcg is not killed when we are reclaiming.
> - */
> spin_unlock(&zswap_shrink_lock);
>
> if (!memcg) {
next prev parent reply other threads:[~2024-08-05 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 5:33 Yosry Ahmed
2024-08-03 21:35 ` Nhat Pham
2024-08-05 2:06 ` Chengming Zhou [this message]
2024-08-05 17:06 ` Johannes Weiner
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=a3fc7bc6-d9c0-43e2-a530-4dafff61203b@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