From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: "yohan.joung" <yohan.joung@sk.com>, jaegeuk@kernel.org
Cc: pilhyun.kim@sk.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to check upper boundary for value of gc_boost_zoned_gc_percent
Date: Wed, 25 Jun 2025 10:22:56 +0800 [thread overview]
Message-ID: <c5109563-a233-42f2-946e-e5b7339a03d5@kernel.org> (raw)
In-Reply-To: <20250625001408.1961-1-yohan.joung@sk.com>
On 6/25/25 08:14, yohan.joung wrote:
> to check the upper boundary when setting gc_boost_zoned_gc_percent
>
> Signed-off-by: yohan.joung <yohan.joung@sk.com>
Fixes: 9a481a1c16f4 ("f2fs: create gc_no_zoned_gc_percent and gc_boost_zoned_gc_percent")
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-06-25 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 0:14 [f2fs-dev] [PATCH] f2fs: fix to check upper boundary for value of gc_boost_zoned_gc_percent yohan.joung
2025-06-25 2:22 ` Chao Yu via Linux-f2fs-devel [this message]
2025-07-09 18:10 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
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=c5109563-a233-42f2-946e-e5b7339a03d5@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pilhyun.kim@sk.com \
--cc=yohan.joung@sk.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).