linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: yonggil.song@samsung.com,
	"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [f2fs-dev] [PATCH v1] f2fs: avoid victim selection from previous victim section
Date: Tue, 22 Nov 2022 16:01:54 +0800	[thread overview]
Message-ID: <af5ae747-5552-aeb0-885e-ddc9ab6f39c3@kernel.org> (raw)
In-Reply-To: <20221122023656epcms2p4468d4feb97711516206e19890dad09ac@epcms2p4>

Hi Yonggil,

I guess your email client forces converting tab and space characters of
patch, please check that.

On 2022/11/22 10:36, Yonggil Song wrote:
> When f2fs chooses GC victim in large section & LFS mode,
> next_victim_seg[gc_type] is referenced first. After segment is freed,
> next_victim_seg[gc_type] has the next segment number.
> However, next_victim_seg[gc_type] still has the last segment number
> even after the last segment of section is freed. In this case, when f2fs
> chooses a victim for the next GC round, the last segment of previous victim
> section is chosen as a victim.
> 
> Initialize next_victim_seg[gc_type] to NULL_SEGNO for the last segment in
> large section.
> 
> Fixes: e3080b0120a1 ("f2fs: support subsectional garbage collection")

Good catch, I'm fine with this fix.

Thanks,

> Signed-off-by: Yonggil Song <yonggil.song@samsung.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 4546e01b2ee0..10677d53ef0e 100644
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -1744,8 +1744,9 @@ static int do_garbage_collect(struct f2fs_sb_info *sbi,
>                                   get_valid_blocks(sbi, segno, false) == 0)
>                           seg_freed++;
>   
> -                if (__is_large_section(sbi) && segno + 1 < end_segno)
> -                        sbi->next_victim_seg[gc_type] = segno + 1;
> +                if (__is_large_section(sbi))
> +                        sbi->next_victim_seg[gc_type] =
> +                                (segno + 1 < end_segno) ? segno + 1 : NULL_SEGNO;
>   skip:
>                   f2fs_put_page(sum_page, 0);
>           }
> -- 
> 2.34.1


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2022-11-22  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221102100756epcms2p23dfabe90c467313ce094c5c81a99c6d7@epcms2p4>
2022-11-22  2:36 ` [f2fs-dev] [PATCH v1] f2fs: avoid victim selection from previous victim section Yonggil Song
2022-11-22  8:01   ` Chao Yu [this message]
     [not found]   ` <CGME20221102100756epcms2p23dfabe90c467313ce094c5c81a99c6d7@epcms2p5>
2022-11-22  8:56     ` [f2fs-dev] (2) " Yonggil Song
     [not found] <CGME20221102100756epcms2p23dfabe90c467313ce094c5c81a99c6d7@epcms2p7>
2022-11-15  0:45 ` [f2fs-dev] " Yonggil Song
     [not found] <CGME20221102100756epcms2p23dfabe90c467313ce094c5c81a99c6d7@epcms2p2>
2022-11-02 10:07 ` 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=af5ae747-5552-aeb0-885e-ddc9ab6f39c3@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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).