From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to trigger a checkpoint in the end of foreground garbage collection
Date: Tue, 18 Apr 2023 23:51:26 +0800 [thread overview]
Message-ID: <2ad8e637-6914-2d3e-3cfa-5f0f7f5ccaea@kernel.org> (raw)
In-Reply-To: <ZDhXNMkgnmjccIhF@google.com>
On 2023/4/14 3:25, Jaegeuk Kim wrote:
> Fixed a xfstests failure.
>
> From 400c722c2117660b83190c88e5442d63fbbffe6e Mon Sep 17 00:00:00 2001
> From: Jaegeuk Kim <jaegeuk@kernel.org>
> Date: Mon, 10 Apr 2023 14:48:50 -0700
> Subject: [PATCH] f2fs: refactor f2fs_gc to call checkpoint in urgent condition
>
> The major change is to call checkpoint, if there's not enough space while having
> some prefree segments in FG_GC case.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
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
prev parent reply other threads:[~2023-04-18 15:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 7:10 [f2fs-dev] [PATCH] f2fs: fix to trigger a checkpoint in the end of foreground garbage collection Chao Yu
2023-04-03 18:13 ` Jaegeuk Kim
2023-04-04 10:46 ` Chao Yu
2023-04-04 21:39 ` Jaegeuk Kim
2023-04-05 2:02 ` Chao Yu
2023-04-05 15:55 ` Jaegeuk Kim
2023-04-10 13:52 ` Chao Yu
2023-04-10 23:21 ` Jaegeuk Kim
2023-04-13 9:15 ` Chao Yu
2023-04-13 15:56 ` Jaegeuk Kim
2023-04-13 15:58 ` Jaegeuk Kim
2023-04-13 19:25 ` Jaegeuk Kim
2023-04-18 15:51 ` Chao Yu [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=2ad8e637-6914-2d3e-3cfa-5f0f7f5ccaea@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).