From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH 6/7] f2fs: create gc_no_zoned_gc_percent and gc_boost_zoned_gc_percent
Date: Fri, 6 Sep 2024 14:35:23 +0800 [thread overview]
Message-ID: <f4aba59b-21a1-45c8-a8ec-443be37a859a@kernel.org> (raw)
In-Reply-To: <20240829215242.3641502-6-daeho43@gmail.com>
On 2024/8/30 5:52, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Added control knobs for gc_no_zoned_gc_percent and
> gc_boost_zoned_gc_percent.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2024-09-06 6:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 21:52 [PATCH 1/7] f2fs: make BG GC more aggressive for zoned devices Daeho Jeong
2024-08-29 21:52 ` [PATCH 2/7] f2fs: read summary blocks with the correct amount for migration_granularity Daeho Jeong
2024-09-06 2:56 ` [f2fs-dev] " Chao Yu
2024-09-06 20:23 ` Daeho Jeong
2024-09-09 8:18 ` Chao Yu
2024-08-29 21:52 ` [PATCH 3/7] f2fs: add reserved_segments sysfs node Daeho Jeong
2024-09-06 3:04 ` [f2fs-dev] " Chao Yu
2024-08-29 21:52 ` [PATCH 4/7] f2fs: increase BG GC migration granularity when boosted for zoned devices Daeho Jeong
2024-09-06 3:37 ` [f2fs-dev] " Chao Yu
2024-08-29 21:52 ` [PATCH 5/7] f2fs: do FG_GC when GC boosting is required " Daeho Jeong
2024-09-06 6:34 ` [f2fs-dev] " Chao Yu
2024-08-29 21:52 ` [PATCH 6/7] f2fs: create gc_no_zoned_gc_percent and gc_boost_zoned_gc_percent Daeho Jeong
2024-09-06 6:35 ` Chao Yu [this message]
2024-08-29 21:52 ` [PATCH 7/7] f2fs: add valid block ratio not to do excessive GC for one time GC Daeho Jeong
2024-09-09 9:22 ` [f2fs-dev] " Chao Yu
2024-09-06 2:21 ` [f2fs-dev] [PATCH 1/7] f2fs: make BG GC more aggressive for zoned devices Chao Yu
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=f4aba59b-21a1-45c8-a8ec-443be37a859a@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome