mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yunlong Song <yunlong.song@huawei.com>
To: Chao Yu <yuchao0@huawei.com>, <jaegeuk@kernel.org>,
	<chao@kernel.org>, <yunlong.song@icloud.com>
Cc: <miaoxie@huawei.com>, <bintian.wang@huawei.com>,
	<shengyong1@huawei.com>, <heyunlei@huawei.com>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] f2fs: clear the remaining prefree_map of the section
Date: Tue, 17 Jul 2018 17:53:44 +0800	[thread overview]
Message-ID: <00b0826b-f1f9-31bb-60a1-cc0a9be90dfa@huawei.com> (raw)
In-Reply-To: <b81bb907-44cd-4cf3-4ddf-a759adec61fb@huawei.com>



On 2018/7/17 17:05, Chao Yu wrote:
> On 2018/7/16 18:03, Yunlong Song wrote:
>> For the case when sbi->segs_per_sec > 1 with lfs mode, take
>> section:segment = 5 for example, if the section prefree_map is
>> ...previous section | current section (1 1 0 1 1) | next section...,
>> then the start = x, end = x + 1, after start = start_segno +
>> sbi->segs_per_sec, start = x + 5, then it will skip x + 3 and x + 4, but
>> their bitmap is still set, which will cause duplicated
>> f2fs_issue_discard of this same section in the next write_checkpoint, so
>> fix it.
> I mean:
>
> Subject: [PATCH] f2fs: issue discard align to section in LFS mode
>
> ---
>   fs/f2fs/segment.c | 19 ++++++++++++++++---
>   1 file changed, 16 insertions(+), 3 deletions(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index f12dad627fb4..6640c790cf64 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -1761,6 +1761,7 @@ void f2fs_clear_prefree_segments(struct f2fs_sb_info *sbi,
>   	unsigned int start = 0, end = -1;
>   	unsigned int secno, start_segno;
>   	bool force = (cpc->reason & CP_DISCARD);
> +	bool need_align = test_opt(sbi, LFS) && sbi->segs_per_sec > 1;
>
>   	mutex_lock(&dirty_i->seglist_lock);
>
> @@ -1772,10 +1773,15 @@ void f2fs_clear_prefree_segments(struct f2fs_sb_info *sbi,
>   		end = find_next_zero_bit(prefree_map, MAIN_SEGS(sbi),
>   								start + 1);
>
> -		for (i = start; i < end; i++)
> -			clear_bit(i, prefree_map);
> +		if (need_align) {
> +			start = rounddown(start, sbi->segs_per_sec);
> +			end = roundup(start, sbi->segs_per_sec);
> +		}
>
> -		dirty_i->nr_dirty[PRE] -= end - start;
> +		for (i = start; i < end; i++) {
> +			if (test_and_clear_bit(i, prefree_map))
> +				dirty_i->nr_dirty[PRE]--;
> +		}
The above part should be put below if (!test_opt(sbi, DISCARD)), or in 
test_opt(sbi, DISCARD) == 0 case,
the first segment of the next section will be skipped, if only the first 
segment is prefree and all the other
segments of the section are not prefree.

>   		if (!test_opt(sbi, DISCARD))
>   			continue;
> @@ -2564,6 +2570,7 @@ int f2fs_trim_fs(struct f2fs_sb_info *sbi, struct fstrim_range *range)
>   	struct discard_policy dpolicy;
>   	unsigned long long trimmed = 0;
>   	int err = 0;
> +	bool need_align = test_opt(sbi, LFS) && sbi->segs_per_sec > 1;
>
>   	if (start >= MAX_BLKADDR(sbi) || range->len < sbi->blocksize)
>   		return -EINVAL;
> @@ -2582,6 +2589,12 @@ int f2fs_trim_fs(struct f2fs_sb_info *sbi, struct fstrim_range *range)
>   	end_segno = (end >= MAX_BLKADDR(sbi)) ? MAIN_SEGS(sbi) - 1 :
>   						GET_SEGNO(sbi, end);
>
> +	if (need_align) {
> +		start_segno = rounddown(start_segno, sbi->segs_per_sec);
> +		end_segno = roundup(end_segno, sbi->segs_per_sec);
> +		end_segno = min(end_segno, MAIN_SEGS(sbi) - 1);
> +	}
> +
>   	cpc.reason = CP_DISCARD;
>   	cpc.trim_minlen = max_t(__u64, 1, F2FS_BYTES_TO_BLK(range->minlen));
>   	cpc.trim_start = start_segno;

-- 
Thanks,
Yunlong Song



      reply	other threads:[~2018-07-17  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 10:03 Yunlong Song
2018-07-17  9:05 ` Chao Yu
2018-07-17  9:53   ` Yunlong Song [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=00b0826b-f1f9-31bb-60a1-cc0a9be90dfa@huawei.com \
    --to=yunlong.song@huawei.com \
    --cc=bintian.wang@huawei.com \
    --cc=chao@kernel.org \
    --cc=heyunlei@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=shengyong1@huawei.com \
    --cc=yuchao0@huawei.com \
    --cc=yunlong.song@icloud.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

all inboxes | Powered by JetHome®