From: Chao Yu <chao@kernel.org>
To: Yunlong Song <yunlong.song@huawei.com>,
jaegeuk@kernel.org, yuchao0@huawei.com, yunlong.song@icloud.com
Cc: 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 v2] f2fs: free_user_blocks should use reserved_segments instead
Date: Fri, 18 Aug 2017 23:19:53 +0800 [thread overview]
Message-ID: <42326662-a08f-d140-89f0-d7364e088903@kernel.org> (raw)
In-Reply-To: <624b1f95-1b48-1b2e-4e9a-27d19859b878@huawei.com>
Hi Yunlong,
I think you have changed original implication of the function, IMO, it would be
more accurate to use user_free_segment_blocks instead of free_user_blocks.
Thanks,
On 2017/8/18 18:02, Yunlong Song wrote:
> ping...
>
> On 2017/8/15 15:14, Yunlong Song wrote:
>> 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.
>>
>> Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
>> ---
>> fs/f2fs/gc.h | 18 +++++++++++++++---
>> 1 file changed, 15 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/f2fs/gc.h b/fs/f2fs/gc.h
>> index 9325191..542612a 100644
>> --- a/fs/f2fs/gc.h
>> +++ b/fs/f2fs/gc.h
>> @@ -49,11 +49,23 @@ struct gc_inode_list {
>> */
>> static inline block_t free_user_blocks(struct f2fs_sb_info *sbi)
>> {
>> - if (free_segments(sbi) < overprovision_segments(sbi))
>> + block_t avail_user_block_count, free_blocks, avail_free_blocks;
>> + block_t reserved_blocks;
>> +
>> + avail_user_block_count = sbi->user_block_count - sbi->reserved_blocks;
>> +
>> + if (unlikely(sbi->total_valid_block_count > avail_user_block_count))
>> + return 0;
>> +
>> + free_blocks = free_segments(sbi) << sbi->log_blocks_per_seg;
>> + avail_free_blocks = min(free_blocks, avail_user_block_count -
>> + sbi->total_valid_block_count);
>> + reserved_blocks = reserved_segments(sbi) << sbi->log_blocks_per_seg;
>> +
>> + if (avail_free_blocks < reserved_blocks)
>> return 0;
>> else
>> - return (free_segments(sbi) - overprovision_segments(sbi))
>> - << sbi->log_blocks_per_seg;
>> + return avail_free_blocks - reserved_blocks;
>> }
>> static inline block_t limit_invalid_user_blocks(struct f2fs_sb_info *sbi)
>
prev parent reply other threads:[~2017-08-18 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 9:22 [PATCH] f2fs: free_user_blocks should use reserved_segments instead Yunlong Song
2017-08-15 3:32 ` Jaegeuk Kim
2017-08-15 7:17 ` Yunlong Song
2017-08-15 7:14 ` [PATCH v2] " Yunlong Song
2017-08-18 10:02 ` Yunlong Song
2017-08-18 15:19 ` 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=42326662-a08f-d140-89f0-d7364e088903@kernel.org \
--to=chao@kernel.org \
--cc=bintian.wang@huawei.com \
--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@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;
as well as URLs for NNTP newsgroup(s).