From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: report # of free inodes more precisely
Date: Mon, 26 Jun 2017 18:52:39 +0800 [thread overview]
Message-ID: <2d091ab2-cf3a-5185-99d1-59c606c9b9dc@huawei.com> (raw)
In-Reply-To: <20170624162522.48931-2-jaegeuk@kernel.org>
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?
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;
>
next prev parent reply other threads:[~2017-06-26 10:53 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 ` Chao Yu [this message]
2017-06-26 14:58 ` [f2fs-dev] " Jaegeuk Kim
2017-06-28 13:01 ` Chao Yu
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=2d091ab2-cf3a-5185-99d1-59c606c9b9dc@huawei.com \
--to=yuchao0@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 \
/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®