From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
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 v3] f2fs: add gc_boost_gc_greedy sysfs node
Date: Tue, 29 Jul 2025 11:07:50 +0800 [thread overview]
Message-ID: <10a7334c-29be-4f04-8e4f-746491959ef1@kernel.org> (raw)
In-Reply-To: <20250728170430.1060976-1-daeho43@gmail.com>
On 7/29/25 01:04, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Add this to control GC algorithm for boost GC.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
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
WARNING: multiple messages have this Message-ID (diff)
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: chao@kernel.org, Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: add gc_boost_gc_greedy sysfs node
Date: Tue, 29 Jul 2025 11:07:50 +0800 [thread overview]
Message-ID: <10a7334c-29be-4f04-8e4f-746491959ef1@kernel.org> (raw)
In-Reply-To: <20250728170430.1060976-1-daeho43@gmail.com>
On 7/29/25 01:04, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Add this to control GC algorithm for boost GC.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-07-29 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 17:04 [f2fs-dev] [PATCH v3] f2fs: add gc_boost_gc_greedy sysfs node Daeho Jeong
2025-07-28 17:04 ` Daeho Jeong
2025-07-29 3:07 ` Chao Yu via Linux-f2fs-devel [this message]
2025-07-29 3:07 ` [f2fs-dev] " 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=10a7334c-29be-4f04-8e4f-746491959ef1@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.