public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: fix to trigger a checkpoint in the end of foreground garbage collection
Date: Mon, 3 Apr 2023 11:13:26 -0700	[thread overview]
Message-ID: <ZCsXRin7symPxIrn@google.com> (raw)
In-Reply-To: <20230324071028.336982-1-chao@kernel.org>

On 03/24, Chao Yu wrote:
> In order to reclaim free blocks in prefree sections before latter use.

We were supposed to do checkpoint as is?

> 
> Fixes: 6f8d4455060d ("f2fs: avoid fi->i_gc_rwsem[WRITE] lock in f2fs_gc")
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
>  fs/f2fs/f2fs.h    | 1 +
>  fs/f2fs/gc.c      | 8 ++++++++
>  fs/f2fs/segment.c | 1 +
>  3 files changed, 10 insertions(+)
> 
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index 53a005b420cf..b1515375cb4c 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -1269,6 +1269,7 @@ struct f2fs_gc_control {
>  	unsigned int victim_segno;	/* target victim segment number */
>  	int init_gc_type;		/* FG_GC or BG_GC */
>  	bool no_bg_gc;			/* check the space and stop bg_gc */
> +	bool reclaim_space;		/* trigger checkpoint to reclaim space */
>  	bool should_migrate_blocks;	/* should migrate blocks */
>  	bool err_gc_skipped;		/* return EAGAIN if GC skipped */
>  	unsigned int nr_free_secs;	/* # of free sections to do GC */
> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> index 2996d38aa89c..5a451d3d512d 100644
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -132,6 +132,7 @@ static int gc_thread_func(void *data)
>  
>  		gc_control.init_gc_type = sync_mode ? FG_GC : BG_GC;
>  		gc_control.no_bg_gc = foreground;
> +		gc_control.reclaim_space = foreground;
>  		gc_control.nr_free_secs = foreground ? 1 : 0;
>  
>  		/* if return value is not zero, no victim was selected */
> @@ -1880,6 +1881,13 @@ int f2fs_gc(struct f2fs_sb_info *sbi, struct f2fs_gc_control *gc_control)
>  				(gc_type == FG_GC) ? sec_freed : 0, 0)) {
>  		if (gc_type == FG_GC && sec_freed < gc_control->nr_free_secs)
>  			goto go_gc_more;
> +
> +		/*
> +		 * trigger a checkpoint in the end of foreground garbage
> +		 * collection.
> +		 */
> +		if (gc_control->reclaim_space)
> +			ret = f2fs_write_checkpoint(sbi, &cpc);
>  		goto stop;
>  	}
>  
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 6c11789da884..b62af2ae1685 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -421,6 +421,7 @@ void f2fs_balance_fs(struct f2fs_sb_info *sbi, bool need)
>  				.victim_segno = NULL_SEGNO,
>  				.init_gc_type = BG_GC,
>  				.no_bg_gc = true,
> +				.reclaim_space = true,
>  				.should_migrate_blocks = false,
>  				.err_gc_skipped = false,
>  				.nr_free_secs = 1 };
> -- 
> 2.25.1

  reply	other threads:[~2023-04-03 18:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24  7:10 [PATCH] f2fs: fix to trigger a checkpoint in the end of foreground garbage collection Chao Yu
2023-04-03 18:13 ` Jaegeuk Kim [this message]
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               ` [f2fs-dev] " Jaegeuk Kim
2023-04-13 19:25                 ` Jaegeuk Kim
2023-04-18 15:51                   ` 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=ZCsXRin7symPxIrn@google.com \
    --to=jaegeuk@kernel.org \
    --cc=chao@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