From: patchwork-bot+f2fs@kernel.org
To: Yonggil Song <yonggil.song@samsung.com>
Cc: linux-kernel@vger.kernel.org, beomsu7.kim@samsung.com,
sukka.kim@samsung.com, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v1] f2fs: Fix over-estimating free section during FG GC
Date: Thu, 18 May 2023 01:50:21 +0000 [thread overview]
Message-ID: <168437462160.19511.13019487085074367761.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230512041610epcms2p506e7539079670524146ba6eeeb9dbd63@epcms2p5>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 12 May 2023 13:16:10 +0900 you wrote:
> There was a bug that finishing FG GC unconditionally because free sections
> are over-estimated after checkpoint in FG GC.
> This patch initializes sec_freed by every checkpoint in FG GC.
>
> Signed-off-by: Yonggil Song <yonggil.song@samsung.com>
> ---
> fs/f2fs/gc.c | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
Here is the summary with links:
- [f2fs-dev,v1] f2fs: Fix over-estimating free section during FG GC
https://git.kernel.org/jaegeuk/f2fs/c/62c85994b958
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-05-18 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230512041610epcms2p506e7539079670524146ba6eeeb9dbd63@epcms2p5>
2023-05-12 4:16 ` [f2fs-dev] [PATCH v1] f2fs: Fix over-estimating free section during FG GC Yonggil Song
2023-05-17 2:40 ` Chao Yu
2023-05-18 1:50 ` patchwork-bot+f2fs [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=168437462160.19511.13019487085074367761.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=beomsu7.kim@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sukka.kim@samsung.com \
--cc=yonggil.song@samsung.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).