From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Weichao Guo <guoweichao@huawei.com>
Cc: huxinwei@huawei.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: fix BG_GC count stat & f2fs_gc return value
Date: Mon, 8 May 2017 13:36:32 -0700 [thread overview]
Message-ID: <20170508203632.GA47455@jaegeuk.local> (raw)
In-Reply-To: <20170505180728.235186-1-guoweichao@huawei.com>
Hi Weichao,
On 05/06, Weichao Guo wrote:
> We should call stat_inc_bggc_count only after BG_GC has been performed
> successfully. Otherwise, BG_GC count may be larger than total count when
> f2fs_gc failed, e.g., no victim was selected.
>
> By default, f2fs_gc returns EINVAL in some error cases, e.g., no victim was
> selected. However, the default errno may be overwritten in the case of
> BG_GC -> FG_GC.
Please split this patch into two patches per each issue.
>
> Signed-off-by: Weichao Guo <guoweichao@huawei.com>
> ---
> fs/f2fs/gc.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> index 0265221..a42cafe 100644
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -81,11 +81,11 @@ static int gc_thread_func(void *data)
> else
> increase_sleep_time(gc_th, &wait_ms);
>
> - stat_inc_bggc_count(sbi);
> -
> /* if return value is not zero, no victim was selected */
> if (f2fs_gc(sbi, test_opt(sbi, FORCE_FG_GC), true, NULL_SEGNO))
> wait_ms = gc_th->no_gc_sleep_time;
> + else
> + stat_inc_bggc_count(sbi);
>
> trace_f2fs_background_gc(sbi->sb, wait_ms,
> prefree_segments(sbi), free_segments(sbi));
> @@ -987,6 +987,7 @@ int f2fs_gc(struct f2fs_sb_info *sbi, bool sync,
> gc_type = FG_GC;
> }
>
> + ret = -EINVAL;
It'd be better to set -EINVAL at the beginning of gc_more timing.
Thoughts?
Thanks,
> /* f2fs_balance_fs doesn't need to do BG_GC in critical path. */
> if (gc_type == BG_GC && !background)
> goto stop;
> --
> 2.10.1
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
prev parent reply other threads:[~2017-05-08 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 18:07 [PATCH] f2fs: fix BG_GC count stat & f2fs_gc return value Weichao Guo
2017-05-08 20:36 ` Jaegeuk Kim [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=20170508203632.GA47455@jaegeuk.local \
--to=jaegeuk@kernel.org \
--cc=guoweichao@huawei.com \
--cc=huxinwei@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).