From: Jaegeuk Kim <jaegeuk@kernel.org>
To: heyunlei <heyunlei@huawei.com>
Cc: heyunlei@huwei.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v3] f2fs: fix a missing discard prefree segments
Date: Wed, 21 Dec 2016 18:21:22 -0800 [thread overview]
Message-ID: <20161222022122.GA33509@jaegeuk.local> (raw)
In-Reply-To: <69ab3186-0d74-624b-0d4c-2b10a187c230@huawei.com>
On 12/22, heyunlei wrote:
> Hi Jaegeuk,
>
> On 2016/12/22 2:04, Jaegeuk Kim wrote:
> > On 12/21, Yunlei He wrote:
> > > If userspace issue a fstrim with a range not involve prefree segments,
> > > it will reuse these segments without discard. This patch fix it.
> > >
> > > Signed-off-by: Yunlei He <heyunlei@huawei.com>
> > > ---
> > > fs/f2fs/segment.c | 9 +++++++--
> > > 1 file changed, 7 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> > > index 0738f48..e0fff28 100644
> > > --- a/fs/f2fs/segment.c
> > > +++ b/fs/f2fs/segment.c
> > > @@ -916,9 +916,13 @@ void clear_prefree_segments(struct f2fs_sb_info *sbi, struct cp_control *cpc)
> > >
> > > dirty_i->nr_dirty[PRE] -= end - start;
> > >
> > > - if (force || !test_opt(sbi, DISCARD))
> > > + if (!test_opt(sbi, DISCARD))
> > > continue;
> > >
> > > + if (force && start >= cpc->trim_start &&
> > > + (end -1) <= cpc->trim_end)
> > > + continue;
> > > +
> > > if (!test_opt(sbi, LFS) || sbi->segs_per_sec == 1) {
> > > f2fs_issue_discard(sbi, START_BLOCK(sbi, start),
> > > (end - start) << sbi->log_blocks_per_seg);
> > > @@ -2263,7 +2267,8 @@ void flush_sit_entries(struct f2fs_sb_info *sbi, struct cp_control *cpc)
> > > f2fs_bug_on(sbi, sit_i->dirty_sentries);
> > > out:
> > > if (cpc->reason == CP_DISCARD) {
> > > - for (; cpc->trim_start <= cpc->trim_end; cpc->trim_start++)
> > > + __u64 trim_start = cpc->trim_start;
> > > + for (; trim_start <= cpc->trim_end; trim_start++)
> >
> > BTW, why do we need this?
> > The below add_discard_addrs() will use cpc->trim_start.
>
> Here, we need to reserve the original value of cpc->trim_start, because
> we will use it as a boundary judgement for skipping prefree segments
> discard. How about this:
Looks good to me. :)
Could you send v4?
Thanks,
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 0738f48..30cd445 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -916,9 +916,13 @@ void clear_prefree_segments(struct f2fs_sb_info *sbi, struct cp_control *cpc)
>
> dirty_i->nr_dirty[PRE] -= end - start;
>
> - if (force || !test_opt(sbi, DISCARD))
> + if (!test_opt(sbi, DISCARD))
> continue;
>
> + if (force && start >= cpc->trim_start &&
> + (end -1) <= cpc->trim_end)
> + continue;
> +
> if (!test_opt(sbi, LFS) || sbi->segs_per_sec == 1) {
> f2fs_issue_discard(sbi, START_BLOCK(sbi, start),
> (end - start) << sbi->log_blocks_per_seg);
> @@ -2263,8 +2267,11 @@ void flush_sit_entries(struct f2fs_sb_info *sbi, struct cp_control *cpc)
> f2fs_bug_on(sbi, sit_i->dirty_sentries);
> out:
> if (cpc->reason == CP_DISCARD) {
> + __u64 trim_start = cpc->trim_start;
> for (; cpc->trim_start <= cpc->trim_end; cpc->trim_start++)
> add_discard_addrs(sbi, cpc);
> +
> + cpc->trim_start = trim_start;
> }
> mutex_unlock(&sit_i->sentry_lock);
>
> Thanks,
>
> >
> > Thanks,
> >
> > > add_discard_addrs(sbi, cpc);
> > > }
> > > mutex_unlock(&sit_i->sentry_lock);
> > > --
> > > 2.10.1
> > >
> > >
> > > ------------------------------------------------------------------------------
> > > Developer Access Program for Intel Xeon Phi Processors
> > > Access to Intel Xeon Phi processor-based developer platforms.
> > > With one year of Intel Parallel Studio XE.
> > > Training and support from Colfax.
> > > Order your platform today.http://sdm.link/intel
> > > _______________________________________________
> > > Linux-f2fs-devel mailing list
> > > Linux-f2fs-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> >
> > .
> >
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
prev parent reply other threads:[~2016-12-22 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 9:27 [PATCH v3] f2fs: fix a missing discard prefree segments Yunlei He
2016-12-21 18:04 ` Jaegeuk Kim
2016-12-22 1:54 ` heyunlei
2016-12-22 2:21 ` 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=20161222022122.GA33509@jaegeuk.local \
--to=jaegeuk@kernel.org \
--cc=heyunlei@huawei.com \
--cc=heyunlei@huwei.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).