From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Yonggil Song <yonggil.song@samsung.com>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH] f2fs_io: support checkpoint command
Date: Mon, 17 Apr 2023 14:48:32 -0700 [thread overview]
Message-ID: <ZD2+sJcf3NALjEDC@google.com> (raw)
In-Reply-To: <20230417030715epcms2p23a6154070f7140a5ae49c6e07114b88e@epcms2p2>
On 04/17, Yonggil Song 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>
> >---
> > fs/f2fs/gc.c | 27 +++++++++++++--------------
> > 1 file changed, 13 insertions(+), 14 deletions(-)
> >
> >diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> >index c748cdfb0501..ba5775dcade6 100644
> >--- a/fs/f2fs/gc.c
> >+++ b/fs/f2fs/gc.c
> >@@ -1829,7 +1829,10 @@ int f2fs_gc(struct f2fs_sb_info *sbi, struct f2fs_gc_control *gc_control)
> > goto stop;
> > }
> >
> >- if (gc_type == BG_GC && has_not_enough_free_secs(sbi, 0, 0)) {
> >+ /* Let's run FG_GC, if we don't have enough space. */
> >+ if (has_not_enough_free_secs(sbi, 0, 0)) {
> >+ gc_type = FG_GC;
> >+
>
> Hi, Jaegeuk & Chao
>
> Would it be possible to clarify if this patch is intended to perform checkpoint every gc round?
Intention is to trigger checkpoint when there's not enough free space. So, it's
not for every gc round.
>
> Thanks.
>
> > /*
> > * For example, if there are many prefree_segments below given
> > * threshold, we can make them free by checkpoint. Then, we
> >@@ -1840,8 +1843,6 @@ int f2fs_gc(struct f2fs_sb_info *sbi, struct f2fs_gc_control *gc_control)
> > if (ret)
> > goto stop;
> > }
> >- if (has_not_enough_free_secs(sbi, 0, 0))
> >- gc_type = FG_GC;
> > }
> >
> > /* f2fs_balance_fs doesn't need to do BG_GC in critical path. */
> >@@ -1868,19 +1869,15 @@ int f2fs_gc(struct f2fs_sb_info *sbi, struct f2fs_gc_control *gc_control)
> > if (seg_freed == f2fs_usable_segs_in_sec(sbi, segno))
> > sec_freed++;
> >
> >- if (gc_type == FG_GC)
> >+ if (gc_type == FG_GC) {
> > sbi->cur_victim_sec = NULL_SEGNO;
> >
> >- if (gc_control->init_gc_type == FG_GC ||
> >- !has_not_enough_free_secs(sbi,
> >- (gc_type == FG_GC) ? sec_freed : 0, 0)) {
> >- if (gc_type == FG_GC && sec_freed < gc_control->nr_free_secs)
> >- goto go_gc_more;
> >- goto stop;
> >- }
> >-
> >- /* FG_GC stops GC by skip_count */
> >- if (gc_type == FG_GC) {
> >+ if (!has_not_enough_free_secs(sbi, sec_freed, 0)) {
> >+ if (!gc_control->no_bg_gc &&
> >+ sec_freed < gc_control->nr_free_secs)
> >+ goto go_gc_more;
> >+ goto stop;
> >+ }
> > if (sbi->skipped_gc_rwsem)
> > skipped_round++;
> > round++;
> >@@ -1889,6 +1886,8 @@ int f2fs_gc(struct f2fs_sb_info *sbi, struct f2fs_gc_control *gc_control)
> > ret = f2fs_write_checkpoint(sbi, &cpc);
> > goto stop;
> > }
> >+ } else if (!has_not_enough_free_secs(sbi, 0, 0)) {
> >+ goto stop;
> > }
> >
> > __get_secs_required(sbi, NULL, &upper_secs, NULL);
> >--
> >2.40.0.634.g4ca3ef3211-goog
> >
> >
> >
> >_______________________________________________
> >Linux-f2fs-devel mailing list
> >Linux-f2fs-devel@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
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:[~2023-04-17 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230414035331epcas2p2bdf8280ca5eb9a5050dd2cc5dfff0f14@epcms2p2>
2023-04-14 3:51 ` [f2fs-dev] [PATCH] f2fs_io: support checkpoint command Chao Yu
2023-04-17 3:07 ` Yonggil Song
2023-04-17 21:48 ` Jaegeuk Kim [this message]
2023-04-18 1:27 ` [f2fs-dev] (2) " Yonggil Song
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=ZD2+sJcf3NALjEDC@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 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.