From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, jeffm@suse.com
Subject: Re: [PATCH 1/6] btrfs: qgroup: Skeleton to support separate qgroup reservation type
Date: Tue, 24 Oct 2017 14:00:19 +0300 [thread overview]
Message-ID: <5e6a7a3c-21ce-12e4-1bdc-78cdcb69d6c7@suse.com> (raw)
In-Reply-To: <20171024083941.21428-2-wqu@suse.com>
On 24.10.2017 11:39, Qu Wenruo wrote:
> Instead of single qgroup->reserved, use a new structure btrfs_qgroup_rsv
> to restore different types of reservation.
>
> This patch only updates the header and needed modification to pass
> compile.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
> fs/btrfs/qgroup.c | 16 ++++++++++------
> fs/btrfs/qgroup.h | 27 +++++++++++++++++++++++++--
> 2 files changed, 35 insertions(+), 8 deletions(-)
>
> diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
> index e172d4843eae..fe3adb996883 100644
> --- a/fs/btrfs/qgroup.c
> +++ b/fs/btrfs/qgroup.c
> @@ -2444,7 +2444,8 @@ static int qgroup_reserve(struct btrfs_root *root, u64 num_bytes, bool enforce)
> }
>
> void btrfs_qgroup_free_refroot(struct btrfs_fs_info *fs_info,
> - u64 ref_root, u64 num_bytes)
> + u64 ref_root, u64 num_bytes,
> + enum btrfs_qgroup_rsv_type type)
> {
> struct btrfs_root *quota_root;
> struct btrfs_qgroup *qgroup;
> @@ -2936,7 +2937,8 @@ static int qgroup_free_reserved_data(struct inode *inode,
> goto out;
> freed += changeset.bytes_changed;
> }
> - btrfs_qgroup_free_refroot(root->fs_info, root->objectid, freed);
> + btrfs_qgroup_free_refroot(root->fs_info, root->objectid, freed,
> + BTRFS_QGROUP_RSV_DATA);
> ret = freed;
> out:
> extent_changeset_release(&changeset);
> @@ -2968,7 +2970,7 @@ static int __btrfs_qgroup_release_data(struct inode *inode,
> if (free)
> btrfs_qgroup_free_refroot(BTRFS_I(inode)->root->fs_info,
> BTRFS_I(inode)->root->objectid,
> - changeset.bytes_changed);
> + changeset.bytes_changed, BTRFS_QGROUP_RSV_DATA);
> ret = changeset.bytes_changed;
> out:
> extent_changeset_release(&changeset);
> @@ -3045,7 +3047,8 @@ void btrfs_qgroup_free_meta_all(struct btrfs_root *root)
> if (reserved == 0)
> return;
> trace_qgroup_meta_reserve(root, -(s64)reserved);
> - btrfs_qgroup_free_refroot(fs_info, root->objectid, reserved);
> + btrfs_qgroup_free_refroot(fs_info, root->objectid, reserved,
> + BTRFS_QGROUP_RSV_META);
> }
>
> void btrfs_qgroup_free_meta(struct btrfs_root *root, int num_bytes)
> @@ -3060,7 +3063,8 @@ void btrfs_qgroup_free_meta(struct btrfs_root *root, int num_bytes)
> WARN_ON(atomic64_read(&root->qgroup_meta_rsv) < num_bytes);
> atomic64_sub(num_bytes, &root->qgroup_meta_rsv);
> trace_qgroup_meta_reserve(root, -(s64)num_bytes);
> - btrfs_qgroup_free_refroot(fs_info, root->objectid, num_bytes);
> + btrfs_qgroup_free_refroot(fs_info, root->objectid, num_bytes,
> + BTRFS_QGROUP_RSV_META);
> }
>
> /*
> @@ -3088,7 +3092,7 @@ void btrfs_qgroup_check_reserved_leak(struct inode *inode)
> }
> btrfs_qgroup_free_refroot(BTRFS_I(inode)->root->fs_info,
> BTRFS_I(inode)->root->objectid,
> - changeset.bytes_changed);
> + changeset.bytes_changed, BTRFS_QGROUP_RSV_DATA);
>
> }
> extent_changeset_release(&changeset);
> diff --git a/fs/btrfs/qgroup.h b/fs/btrfs/qgroup.h
> index d9984e87cddf..0b04cbc5b5ce 100644
> --- a/fs/btrfs/qgroup.h
> +++ b/fs/btrfs/qgroup.h
> @@ -61,6 +61,26 @@ struct btrfs_qgroup_extent_record {
> struct ulist *old_roots;
> };
>
> +enum btrfs_qgroup_rsv_type {
> + BTRFS_QGROUP_RSV_DATA = 0,
> + BTRFS_QGROUP_RSV_META = 1,
> + BTRFS_QGROUP_RSV_TYPES = 1,
nit: Why not BTRFS_QGROUP_RSV_TYPES_MAX = 2;
> +};
> +
> +/*
> + * Represents how many bytes we reserved for this qgroup.
> + *
> + * Each type should have different reservation behavior.
> + * E.g, data follows its io_tree flag modification, while
> + * *currently* meta is just reserve-and-clear during transcation.
> + *
> + * TODO: Add new type for delalloc, which can exist across several
> + * transaction.
> + */
> +struct btrfs_qgroup_rsv {
> + u64 values[BTRFS_QGROUP_RSV_TYPES + 1];
nit: And here just BTRFS_QGROUP_RSV_TYPES_MAX rather than the +1 here,
seems more idiomatic to me.
> +};
> +
> /*
> * one struct for each qgroup, organized in fs_info->qgroup_tree.
> */
> @@ -88,6 +108,7 @@ struct btrfs_qgroup {
> * reservation tracking
> */
> u64 reserved;
> + struct btrfs_qgroup_rsv rsv;
>
> /*
> * lists
> @@ -228,12 +249,14 @@ int btrfs_qgroup_inherit(struct btrfs_trans_handle *trans,
> struct btrfs_fs_info *fs_info, u64 srcid, u64 objectid,
> struct btrfs_qgroup_inherit *inherit);
> void btrfs_qgroup_free_refroot(struct btrfs_fs_info *fs_info,
> - u64 ref_root, u64 num_bytes);
> + u64 ref_root, u64 num_bytes,
> + enum btrfs_qgroup_rsv_type type);
> static inline void btrfs_qgroup_free_delayed_ref(struct btrfs_fs_info *fs_info,
> u64 ref_root, u64 num_bytes)
> {
> trace_btrfs_qgroup_free_delayed_ref(fs_info, ref_root, num_bytes);
> - btrfs_qgroup_free_refroot(fs_info, ref_root, num_bytes);
> + btrfs_qgroup_free_refroot(fs_info, ref_root, num_bytes,
> + BTRFS_QGROUP_RSV_DATA);
> }
>
> #ifdef CONFIG_BTRFS_FS_RUN_SANITY_TESTS
>
next prev parent reply other threads:[~2017-10-24 11:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 8:39 [PATCH 0/6] btrfs: qgroup: Separate qgroup reservation types Qu Wenruo
2017-10-24 8:39 ` [PATCH 1/6] btrfs: qgroup: Skeleton to support separate qgroup reservation type Qu Wenruo
2017-10-24 11:00 ` Nikolay Borisov [this message]
2017-10-24 11:51 ` Qu Wenruo
2017-10-24 12:23 ` Nikolay Borisov
2017-10-24 12:36 ` Qu Wenruo
2017-10-24 12:29 ` Jeff Mahoney
2017-10-24 12:40 ` Jeff Mahoney
2017-10-24 12:41 ` Qu Wenruo
2017-10-24 8:39 ` [PATCH 2/6] btrfs: qgroup: Introduce helpers to update and access new qgroup rsv Qu Wenruo
2017-10-24 11:07 ` Nikolay Borisov
2017-10-24 12:05 ` Qu Wenruo
2017-10-24 16:22 ` Edmund Nadolski
2017-10-25 0:38 ` Qu Wenruo
2017-10-24 8:39 ` [PATCH 3/6] btrfs: qgroup: Make qgroup_reserve and its callers to use separate reservation type Qu Wenruo
2017-10-24 8:39 ` [PATCH 4/6] btrfs: qgroup: Fix wrong qgroup reservation inheritance for relationship update Qu Wenruo
2017-10-24 12:01 ` Nikolay Borisov
2017-10-24 12:19 ` Qu Wenruo
2017-10-24 12:28 ` Nikolay Borisov
2017-10-24 17:11 ` Edmund Nadolski
2017-10-25 0:11 ` Qu Wenruo
2017-10-24 8:39 ` [PATCH 5/6] btrfs: qgroup: Update trace events to use new separate rsv types Qu Wenruo
2017-10-24 8:39 ` [PATCH 6/6] btrfs: qgroup: Cleanup the remaining old reservation counters Qu Wenruo
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=5e6a7a3c-21ce-12e4-1bdc-78cdcb69d6c7@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.cz \
--cc=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@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).