From: Chengming Zhou <chengming.zhou@linux.dev>
To: Alice Ryhl <aliceryhl@google.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] mm/zswap: add LRU_STOP to comment about dropping the lru lock
Date: Thu, 28 Nov 2024 10:32:09 +0800 [thread overview]
Message-ID: <abedc173-0760-41fd-a73d-e84dccfc3209@linux.dev> (raw)
In-Reply-To: <20241127-lru-stop-comment-v1-1-f54a7cba9429@google.com>
On 2024/11/27 21:53, Alice Ryhl wrote:
> This function has been able to return LRU_STOP since commit b49547ade38a
> ("mm/zswap: stop lru list shrinking when encounter warm region"). To
> reduce confusion, update the comment to also list LRU_STOP as an option.
>
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Reviewed-by: Chengming Zhou <chengming.zhou@linux.dev>
Thanks!
> ---
> mm/zswap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/zswap.c b/mm/zswap.c
> index f6316b66fb23..9718c33f8192 100644
> --- a/mm/zswap.c
> +++ b/mm/zswap.c
> @@ -1156,7 +1156,7 @@ static enum lru_status shrink_memcg_cb(struct list_head *item, struct list_lru_o
>
> /*
> * It's safe to drop the lock here because we return either
> - * LRU_REMOVED_RETRY or LRU_RETRY.
> + * LRU_REMOVED_RETRY, LRU_RETRY or LRU_STOP.
> */
> spin_unlock(&l->lock);
>
>
> ---
> base-commit: aaf20f870da056752f6386693cc0d8e25421ef35
> change-id: 20241127-lru-stop-comment-09dab2427b6e
>
> Best regards,
prev parent reply other threads:[~2024-11-28 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 13:53 Alice Ryhl
2024-11-27 14:58 ` Johannes Weiner
2024-11-28 2:32 ` Chengming Zhou [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=abedc173-0760-41fd-a73d-e84dccfc3209@linux.dev \
--to=chengming.zhou@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.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