From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 5/6] btrfs: Remove btrfs_inode from btrfs_delayed_inode_reserve_metadata
Date: Tue, 23 Feb 2021 07:53:43 +0800 [thread overview]
Message-ID: <b44ce4c5-ecc4-2fa0-d2ea-8cc98785dfbd@gmx.com> (raw)
In-Reply-To: <20210222164047.978768-6-nborisov@suse.com>
On 2021/2/23 上午12:40, Nikolay Borisov wrote:
> It's only used for tracepoint to obtain the ino, but we already have
> the ino from btrfs_delayed_node::inode_id.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> fs/btrfs/delayed-inode.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/fs/btrfs/delayed-inode.c b/fs/btrfs/delayed-inode.c
> index 6dcf2cd1b39e..875daca63d5d 100644
> --- a/fs/btrfs/delayed-inode.c
> +++ b/fs/btrfs/delayed-inode.c
> @@ -602,7 +602,6 @@ static void btrfs_delayed_item_release_metadata(struct btrfs_root *root,
> static int btrfs_delayed_inode_reserve_metadata(
> struct btrfs_trans_handle *trans,
> struct btrfs_root *root,
> - struct btrfs_inode *inode,
> struct btrfs_delayed_node *node)
> {
> struct btrfs_fs_info *fs_info = root->fs_info;
> @@ -647,7 +646,7 @@ static int btrfs_delayed_inode_reserve_metadata(
> node->bytes_reserved = num_bytes;
> trace_btrfs_space_reservation(fs_info,
> "delayed_inode",
> - btrfs_ino(inode),
> + node->inode_id,
> num_bytes, 1);
> } else {
> btrfs_qgroup_free_meta_prealloc(root, num_bytes);
> @@ -658,7 +657,7 @@ static int btrfs_delayed_inode_reserve_metadata(
> ret = btrfs_block_rsv_migrate(src_rsv, dst_rsv, num_bytes, true);
> if (!ret) {
> trace_btrfs_space_reservation(fs_info, "delayed_inode",
> - btrfs_ino(inode), num_bytes, 1);
> + node->inode_id, num_bytes, 1);
> node->bytes_reserved = num_bytes;
> }
>
> @@ -1833,8 +1832,7 @@ int btrfs_delayed_update_inode(struct btrfs_trans_handle *trans,
> goto release_node;
> }
>
> - ret = btrfs_delayed_inode_reserve_metadata(trans, root, inode,
> - delayed_node);
> + ret = btrfs_delayed_inode_reserve_metadata(trans, root, delayed_node);
> if (ret)
> goto release_node;
>
>
next prev parent reply other threads:[~2021-02-22 23:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 16:40 [PATCH 0/6] Qgroup/delayed node related fixes Nikolay Borisov
2021-02-22 16:40 ` [PATCH 1/6] btrfs: Free correct amount of space in btrfs_delayed_inode_reserve_metadata Nikolay Borisov
2021-02-22 23:41 ` Qu Wenruo
2021-02-22 16:40 ` [PATCH 2/6] btrfs: Export qgroup_reserve_meta Nikolay Borisov
2021-02-22 23:42 ` Qu Wenruo
2021-02-25 16:27 ` David Sterba
2021-02-22 16:40 ` [PATCH 3/6] btrfs: Don't flush from btrfs_delayed_inode_reserve_metadata Nikolay Borisov
2021-02-22 23:45 ` Qu Wenruo
2021-02-22 16:40 ` [PATCH 4/6] btrfs: Cleanup try_flush_qgroup Nikolay Borisov
2021-02-22 23:46 ` Qu Wenruo
2021-02-22 16:40 ` [PATCH 5/6] btrfs: Remove btrfs_inode from btrfs_delayed_inode_reserve_metadata Nikolay Borisov
2021-02-22 23:53 ` Qu Wenruo [this message]
2021-02-22 16:40 ` [PATCH 6/6] btrfs: Simplify code flow in btrfs_delayed_inode_reserve_metadata Nikolay Borisov
2021-03-01 16:15 ` David Sterba
2021-03-01 16:20 ` Nikolay Borisov
2021-03-01 18:54 ` David Sterba
2021-03-01 18:55 ` [PATCH 0/6] Qgroup/delayed node related fixes David Sterba
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=b44ce4c5-ecc4-2fa0-d2ea-8cc98785dfbd@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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).