From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: report # of free inodes more precisely
Date: Wed, 28 Jun 2017 21:01:40 +0800 [thread overview]
Message-ID: <2b10c6e0-50d2-04f6-f7d2-cfc95f90e8e6@kernel.org> (raw)
In-Reply-To: <20170626145846.GB8560@jaegeuk-macbookpro.roam.corp.google.com>
On 2017/6/26 22:58, Jaegeuk Kim wrote:
> On 06/26, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2017/6/25 0:25, Jaegeuk Kim wrote:
>>> If the partition is small, we don't need to report total # of inodes including
>>> hidden free nodes.
>>>
>>> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>>> ---
>>> fs/f2fs/super.c | 14 +++++++++++---
>>> 1 file changed, 11 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
>>> index 8e39b850bfc0..3da6fb276f8b 100644
>>> --- a/fs/f2fs/super.c
>>> +++ b/fs/f2fs/super.c
>>> @@ -680,6 +680,7 @@ static int f2fs_statfs(struct dentry *dentry, struct kstatfs *buf)
>>> struct f2fs_sb_info *sbi = F2FS_SB(sb);
>>> u64 id = huge_encode_dev(sb->s_bdev->bd_dev);
>>> block_t total_count, user_block_count, start_count, ovp_count;
>>> + u64 avail_node_count;
>>>
>>> total_count = le64_to_cpu(sbi->raw_super->block_count);
>>> user_block_count = sbi->user_block_count;
>>> @@ -692,9 +693,16 @@ static int f2fs_statfs(struct dentry *dentry, struct kstatfs *buf)
>>> buf->f_bfree = user_block_count - valid_user_blocks(sbi) + ovp_count;
>>> buf->f_bavail = user_block_count - valid_user_blocks(sbi);
>>>
>>> - buf->f_files = sbi->total_node_count - F2FS_RESERVED_NODE_NUM;
>>> - buf->f_ffree = min(buf->f_files - valid_node_count(sbi),
>>> - buf->f_bavail);
>>> + avail_node_count = sbi->total_node_count - F2FS_RESERVED_NODE_NUM;
>>> +
>>> + if (avail_node_count > user_block_count) {
>>> + buf->f_files = user_block_count;
>>> + buf->f_ffree = buf->f_bavail;
>>
>> f_ffree is limited both by remained free nid count and free block count, so it
>> needs to change like this?
>
> I thought both of them are same, since node block will consume user block. So,
> we don't need to do min() again.
avail_node_count comes from total free nid counts which is limited with
nid_bitmap size, buf->f_bavail comes from total user block count which
can both cosumed by node and data. So the value of them may not be the same.
Thanks,
>
>>
>> if (avail_node_count > user_block_count)
>> avail_node_count = user_block_count;
>>
>> buf->f_files = avail_node_count;
>> buf->f_ffree = min(avail_node_count - valid_node_count(sbi),
>> buf->f_bavail);
>>
>> Thanks,
>>
>>> + } else {
>>> + buf->f_files = avail_node_count;
>>> + buf->f_ffree = min(avail_node_count - valid_node_count(sbi),
>>> + buf->f_bavail);
>>> + }
>>>
>>> buf->f_namelen = F2FS_NAME_LEN;
>>> buf->f_fsid.val[0] = (u32)id;
>>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>
next prev parent reply other threads:[~2017-06-28 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 16:25 [PATCH 1/2] f2fs: avoid deadlock caused by lock order of page and lock_op Jaegeuk Kim
2017-06-24 16:25 ` [PATCH 2/2] f2fs: report # of free inodes more precisely Jaegeuk Kim
2017-06-26 10:52 ` [f2fs-dev] " Chao Yu
2017-06-26 14:58 ` Jaegeuk Kim
2017-06-28 13:01 ` Chao Yu [this message]
2017-07-01 7:27 ` Jaegeuk Kim
2017-07-01 8:28 ` Chao Yu
2017-06-26 8:15 ` [f2fs-dev] [PATCH 1/2] f2fs: avoid deadlock caused by lock order of page and lock_op Chao Yu
2017-06-26 14:54 ` Jaegeuk Kim
2017-06-26 15:42 ` Chao Yu
2017-07-01 7:28 ` Jaegeuk Kim
2017-07-01 8:41 ` Chao Yu
2017-07-01 14:27 ` Jaegeuk Kim
2017-07-05 2:58 ` Chao Yu
2017-07-05 3:28 ` Jaegeuk Kim
2017-07-07 19:13 ` [f2fs-dev] [PATCH 1/2 v2] " Jaegeuk Kim
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=2b10c6e0-50d2-04f6-f7d2-cfc95f90e8e6@kernel.org \
--to=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=yuchao0@huawei.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).