From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/2] btrfs: drop no longer needed atomic allocation for tree mod log operations
Date: Fri, 14 Oct 2022 14:44:31 +0100 [thread overview]
Message-ID: <cover.1665754838.git.fdmanana@suse.com> (raw)
In-Reply-To: <cover.1665656353.git.fdmanana@suse.com>
From: Filipe Manana <fdmanana@suse.com>
We are still doing an atomic memory allocation for tree mod log operations
which is not needed anymore after we switch extent buffer locks to rw
semaphores. This replaces that atomic allocation with a GFP_NOFS one, and
then removes redundant gfp_t argument for btrfs_tree_mod_log_insert_key().
V2: Updated patch 2/2 to also remove the allocation flag from
alloc_tree_mod_elem().
Filipe Manana (2):
btrfs: switch GFP_ATOMIC to GFP_NOFS when fixing up low keys
btrfs: remove gfp_t flag from btrfs_tree_mod_log_insert_key()
fs/btrfs/ctree.c | 16 ++++++++--------
fs/btrfs/tree-mod-log.c | 19 +++++++++----------
fs/btrfs/tree-mod-log.h | 2 +-
3 files changed, 18 insertions(+), 19 deletions(-)
--
2.35.1
next prev parent reply other threads:[~2022-10-14 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 10:36 [PATCH 0/2] btrfs: drop no longer needed atomic allocation for tree mod log operations fdmanana
2022-10-13 10:36 ` [PATCH 1/2] btrfs: switch GFP_ATOMIC to GFP_NOFS when fixing up low keys fdmanana
2022-10-13 10:36 ` [PATCH 2/2] btrfs: remove gfp_t flag from btrfs_tree_mod_log_insert_key() fdmanana
2022-10-14 13:30 ` David Sterba
2022-10-14 13:47 ` Filipe Manana
2022-10-14 13:30 ` [PATCH 0/2] btrfs: drop no longer needed atomic allocation for tree mod log operations David Sterba
2022-10-14 13:44 ` fdmanana [this message]
2022-10-14 13:44 ` [PATCH v2 1/2] btrfs: switch GFP_ATOMIC to GFP_NOFS when fixing up low keys fdmanana
2022-10-14 13:44 ` [PATCH v2 2/2] btrfs: remove gfp_t flag from btrfs_tree_mod_log_insert_key() fdmanana
2022-10-14 14:04 ` [PATCH v2 0/2] btrfs: drop no longer needed atomic allocation for tree mod log operations 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.1665754838.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--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 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).