linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao2.yu@samsung.com>
To: 'Jaegeuk Kim' <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: RE: [PATCH v2] f2fs: fix to correct freed section number during gc
Date: Mon, 28 Sep 2015 17:40:43 +0800	[thread overview]
Message-ID: <006d01d0f9d1$d61bc690$825353b0$@samsung.com> (raw)
In-Reply-To: <20150925180417.GB6269@jaegeuk-mac02.mot.com>

> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Saturday, September 26, 2015 2:04 AM
> To: Chao Yu
> Cc: linux-f2fs-devel@lists.sourceforge.net; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2] f2fs: fix to correct freed section number during gc
> 
> On Fri, Sep 25, 2015 at 05:50:55PM +0800, Chao Yu wrote:
> > This patch fixes to maintain the right section count freed in garbage
> > collecting when triggering a foreground gc.
> >
> > Besides, when a foreground gc is running on current selected section, once
> > we fail to gc one segment, it's better to abandon gcing the left segments
> > in current section, because anyway we will select next victim for
> > foreground gc, so gc on the left segments in previous section will become
> > overhead and also cause the long latency for caller.
> >
> > Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> > ---
> > v2:
> >  o avoid calc the wrong value when freed segments across sections.
> >  fs/f2fs/gc.c | 22 +++++++++++++++++-----
> >  1 file changed, 17 insertions(+), 5 deletions(-)
> >
> > diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> > index e932740..256ebd4 100644
> > --- a/fs/f2fs/gc.c
> > +++ b/fs/f2fs/gc.c
> > @@ -802,7 +802,7 @@ int f2fs_gc(struct f2fs_sb_info *sbi)
> >  	unsigned int segno = NULL_SEGNO;
> >  	unsigned int i;
> >  	int gc_type = BG_GC;
> > -	int nfree = 0;
> > +	int sec_freed = 0, seg_freed;
> >  	int ret = -1;
> >  	struct cp_control cpc;
> >  	struct gc_inode_list gc_list = {
> > @@ -817,7 +817,7 @@ gc_more:
> >  	if (unlikely(f2fs_cp_error(sbi)))
> >  		goto stop;
> >
> > -	if (gc_type == BG_GC && has_not_enough_free_secs(sbi, nfree)) {
> > +	if (gc_type == BG_GC && has_not_enough_free_secs(sbi, sec_freed)) {
> >  		gc_type = FG_GC;
> >  		if (__get_victim(sbi, &segno, gc_type) || prefree_segments(sbi))
> >  			write_checkpoint(sbi, &cpc);
> > @@ -833,13 +833,25 @@ gc_more:
> >  		ra_meta_pages(sbi, GET_SUM_BLOCK(sbi, segno), sbi->segs_per_sec,
> >  								META_SSA);
> >
> > -	for (i = 0; i < sbi->segs_per_sec; i++)
> > -		nfree += do_garbage_collect(sbi, segno + i, &gc_list, gc_type);
> > +	for (i = 0, seg_freed = 0; i < sbi->segs_per_sec; i++) {
> > +		/*
> > +		 * for FG_GC case, halt gcing left segments once failed one
> > +		 * of segments in selected section to avoid long latency.
> > +		 */
> > +		if (!do_garbage_collect(sbi, segno + i, &gc_list, gc_type) &&
> > +				gc_type == FG_GC)
> > +			break;
> > +		if (gc_type == FG_GC)
> > +			seg_freed++;
> > +	}
> 
> How about?
> 
> 	if (i == sbi->segs_per_sec && gc_type == FG_GC)
> 		sec_free++;

I'll update it. See the following v3 patch.

Thanks,

> 
> > +
> > +	if (seg_freed == sbi->segs_per_sec)
> > +		sec_freed++;
> >
> >  	if (gc_type == FG_GC)
> >  		sbi->cur_victim_sec = NULL_SEGNO;
> >
> > -	if (has_not_enough_free_secs(sbi, nfree))
> > +	if (has_not_enough_free_secs(sbi, sec_freed))
> >  		goto gc_more;
> >
> >  	if (gc_type == FG_GC)
> > --
> > 2.5.2

      reply	other threads:[~2015-09-28  9:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25  9:50 [PATCH v2] f2fs: fix to correct freed section number during gc Chao Yu
2015-09-25 18:04 ` Jaegeuk Kim
2015-09-28  9:40   ` 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='006d01d0f9d1$d61bc690$825353b0$@samsung.com' \
    --to=chao2.yu@samsung.com \
    --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).