From: Yunlong Song <yunlong.song@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <chao@kernel.org>, <yuchao0@huawei.com>,
<yunlong.song@icloud.com>, <miaoxie@huawei.com>,
<bintian.wang@huawei.com>, <linux-fsdevel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] f2fs: free_user_blocks should use reserved_segments instead
Date: Tue, 15 Aug 2017 15:17:44 +0800 [thread overview]
Message-ID: <367fde95-a6f6-5600-5eda-df254e4ed03b@huawei.com> (raw)
In-Reply-To: <20170815033258.GD91145@jaegeuk-macbookpro.roam.corp.google.com>
Consider this, I have sent another patch v2, please review.
The part (overprovision_segments - reserved_segments) can still be used for LFS
in some case, e.g., there are lots of invalid block from dirty segments, then
the part (overprovision_segments - reserved_segments) can be safely used. So
free_use_blocks should use reserved_segments instead, rather than directly use
overprovision_segments. BTW, we also add the constraint of sbi->reserved_blocks.
On 2017/8/15 11:32, Jaegeuk Kim wrote:
> On 08/14, Yunlong Song wrote:
>> The part (overprovision_segments - reserved_segments) can still be used for LFS,
>> so free_use_blocks should use reserved_segments instead, rather than use
>> overprovision_segments.
>>
>> Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
>> ---
>> fs/f2fs/gc.h | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/gc.h b/fs/f2fs/gc.h
>> index 9325191..6258305 100644
>> --- a/fs/f2fs/gc.h
>> +++ b/fs/f2fs/gc.h
>> @@ -49,10 +49,10 @@ struct gc_inode_list {
>> */
>> static inline block_t free_user_blocks(struct f2fs_sb_info *sbi)
> NAK. This gives user-visible block count.
>
>> {
>> - if (free_segments(sbi) < overprovision_segments(sbi))
>> + if (free_segments(sbi) < reserved_segments(sbi))
>> return 0;
>> else
>> - return (free_segments(sbi) - overprovision_segments(sbi))
>> + return (free_segments(sbi) - reserved_segments(sbi))
>> << sbi->log_blocks_per_seg;
>> }
>>
>> --
>> 1.8.5.2
> .
>
--
Thanks,
Yunlong Song
next prev parent reply other threads:[~2017-08-15 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 9:22 Yunlong Song
2017-08-15 3:32 ` Jaegeuk Kim
2017-08-15 7:17 ` Yunlong Song [this message]
2017-08-15 7:14 ` [PATCH v2] " Yunlong Song
2017-08-18 10:02 ` Yunlong Song
2017-08-18 15:19 ` Chao Yu
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=367fde95-a6f6-5600-5eda-df254e4ed03b@huawei.com \
--to=yunlong.song@huawei.com \
--cc=bintian.wang@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@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®