From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/6] btrfs: qgroup: remove GFP_ATOMIC usage for ulist
Date: Thu, 31 Aug 2023 08:30:31 +0800 [thread overview]
Message-ID: <cover.1693441298.git.wqu@suse.com> (raw)
[CHANGELOG]
v2:
- Remove the final GFP_ATOMIC ulist usage
This is done by introducing a new list_head, btrfs_qgroup::iterator2,
allowing us to do nested iteration.
This extra nested facility is needed as even if we move the qgroups
collection into one dedicated function, we're reusing the list for
iteration which can lead to unnecessary re-visit of the same qgroup.
Thus we have to support one level of nested iteration.
- Add reviewed by tags from Boris
[REPO]
https://github.com/adam900710/linux/tree/qgroup_mutex
Yep, the branch name shows my previous failed attempt to solve the
problem.
[PROBLEM]
There are quite some GFP_ATOMIC usage for btrfs qgroups, most of them
are for ulists.
Those ulists are just used as a temporary memory to trace the involved
qgroups.
[ENHANCEMENT]
This patchset would address the problem by adding a new list_head called
iterator for btrfs_qgroup.
And all call sites but one of ulist allocation can be migrated to use
the new qgroup_iterator facility to iterate qgroups without any memory
allocation.
The only remaining ulist call site is @qgroups ulist utilized inside
btrfs_qgroup_account_extent(), which is utilized to get all involved
qgroups for both old and new roots.
I tried to extract the qgroups collection code into a dedicate loop
out of qgroup_update_refcnt(), but it would lead to test case failure of
btrfs/028 (accounts underflow).
Thus for now only the safe part is sent to the list.
And BTW since we can skip quite some memory allocation failure handling
(since there is no memory allocation), we also save some lines of code.
Qu Wenruo (6):
btrfs: qgroup: iterate qgroups without memory allocation for
qgroup_reserve()
btrfs: qgroup: use qgroup_iterator facility for
btrfs_qgroup_free_refroot()
btrfs: qgroup: use qgroup_iterator facility for qgroup_convert_meta()
btrfs: qgroup: use qgroup_iterator facility for
__qgroup_excl_accounting()
btrfs: qgroup: use qgroup_iterator facility to replace @tmp ulist of
qgroup_update_refcnt()
btrfs: qgroup: use qgroup_iterator2 facility to replace @qgroups ulist
of qgroup_update_refcnt()
fs/btrfs/qgroup.c | 325 +++++++++++++++++-----------------------------
fs/btrfs/qgroup.h | 12 ++
2 files changed, 130 insertions(+), 207 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-31 0:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 0:30 Qu Wenruo [this message]
2023-08-31 0:30 ` [PATCH v2 1/6] btrfs: qgroup: iterate qgroups without memory allocation for qgroup_reserve() Qu Wenruo
2023-08-31 0:30 ` [PATCH v2 2/6] btrfs: qgroup: use qgroup_iterator facility for btrfs_qgroup_free_refroot() Qu Wenruo
2023-08-31 0:30 ` [PATCH v2 3/6] btrfs: qgroup: use qgroup_iterator facility for qgroup_convert_meta() Qu Wenruo
2023-08-31 0:30 ` [PATCH v2 4/6] btrfs: qgroup: use qgroup_iterator facility for __qgroup_excl_accounting() Qu Wenruo
2023-09-01 13:15 ` David Sterba
2023-08-31 0:30 ` [PATCH v2 5/6] btrfs: qgroup: use qgroup_iterator facility to replace @tmp ulist of qgroup_update_refcnt() Qu Wenruo
2023-09-01 13:16 ` David Sterba
2023-09-02 0:16 ` Qu Wenruo
2023-09-05 13:02 ` David Sterba
2023-08-31 0:30 ` [PATCH v2 6/6] btrfs: qgroup: use qgroup_iterator2 facility to replace @qgroups " Qu Wenruo
2023-09-01 13:19 ` 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=cover.1693441298.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.