From: Filipe Manana <fdmanana@gmail.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>, kernel-team@fb.com
Subject: Re: [PATCH 4/8] btrfs: remove the recursion handling code in locking.c
Date: Mon, 9 Nov 2020 10:20:11 +0000 [thread overview]
Message-ID: <CAL3q7H79FhNTbndm+R63H0EzvuuRpjfkaFWs59HdLT6+U0TNYA@mail.gmail.com> (raw)
In-Reply-To: <c04e7bd2e5294b23eadbcafedca7214f7894c9e9.1604697895.git.josef@toxicpanda.com>
On Fri, Nov 6, 2020 at 9:31 PM Josef Bacik <josef@toxicpanda.com> wrote:
>
> Now that we're no longer using recursion, rip out all of the supporting
> code. Follow up patches will clean up the callers of these functions.
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Looks good, thanks.
> ---
> fs/btrfs/locking.c | 63 ++--------------------------------------------
> 1 file changed, 2 insertions(+), 61 deletions(-)
>
> diff --git a/fs/btrfs/locking.c b/fs/btrfs/locking.c
> index d477df1c67db..9b66154803a7 100644
> --- a/fs/btrfs/locking.c
> +++ b/fs/btrfs/locking.c
> @@ -28,40 +28,16 @@
> * Additionally we need one level nesting recursion, see below. The rwsem
> * implementation does opportunistic spinning which reduces number of times the
> * locking task needs to sleep.
> - *
> - *
> - * Lock recursion
> - * --------------
> - *
> - * A write operation on a tree might indirectly start a look up on the same
> - * tree. This can happen when btrfs_cow_block locks the tree and needs to
> - * lookup free extents.
> - *
> - * btrfs_cow_block
> - * ..
> - * alloc_tree_block_no_bg_flush
> - * btrfs_alloc_tree_block
> - * btrfs_reserve_extent
> - * ..
> - * load_free_space_cache
> - * ..
> - * btrfs_lookup_file_extent
> - * btrfs_search_slot
> - *
> */
>
> /*
> * __btrfs_tree_read_lock: Lock the extent buffer for read.
> * @eb: the eb to be locked
> * @nest: the nesting level to be used for lockdep
> - * @recurse: if this lock is able to be recursed
> + * @recurse: unused.
> *
> * This takes the read lock on the extent buffer, using the specified nesting
> * level for lockdep purposes.
> - *
> - * If you specify recurse = true, then we will allow this to be taken if we
> - * currently own the lock already. This should only be used in specific
> - * usecases, and the subsequent unlock will not change the state of the lock.
> */
> void __btrfs_tree_read_lock(struct extent_buffer *eb, enum btrfs_lock_nesting nest,
> bool recurse)
> @@ -71,31 +47,7 @@ void __btrfs_tree_read_lock(struct extent_buffer *eb, enum btrfs_lock_nesting ne
> if (trace_btrfs_tree_read_lock_enabled())
> start_ns = ktime_get_ns();
>
> - if (unlikely(recurse)) {
> - /* First see if we can grab the lock outright */
> - if (down_read_trylock(&eb->lock))
> - goto out;
> -
> - /*
> - * Ok still doesn't necessarily mean we are already holding the
> - * lock, check the owner.
> - */
> - if (eb->lock_owner != current->pid) {
> - down_read_nested(&eb->lock, nest);
> - goto out;
> - }
> -
> - /*
> - * Ok we have actually recursed, but we should only be recursing
> - * once, so blow up if we're already recursed, otherwise set
> - * ->lock_recursed and carry on.
> - */
> - BUG_ON(eb->lock_recursed);
> - eb->lock_recursed = true;
> - goto out;
> - }
> down_read_nested(&eb->lock, nest);
> -out:
> eb->lock_owner = current->pid;
> trace_btrfs_tree_read_lock(eb, start_ns);
> }
> @@ -136,22 +88,11 @@ int btrfs_try_tree_write_lock(struct extent_buffer *eb)
> }
>
> /*
> - * Release read lock. If the read lock was recursed then the lock stays in the
> - * original state that it was before it was recursively locked.
> + * Release read lock.
> */
> void btrfs_tree_read_unlock(struct extent_buffer *eb)
> {
> trace_btrfs_tree_read_unlock(eb);
> - /*
> - * if we're nested, we have the write lock. No new locking
> - * is needed as long as we are the lock owner.
> - * The write unlock will do a barrier for us, and the lock_recursed
> - * field only matters to the lock owner.
> - */
> - if (eb->lock_recursed && current->pid == eb->lock_owner) {
> - eb->lock_recursed = false;
> - return;
> - }
> eb->lock_owner = 0;
> up_read(&eb->lock);
> }
> --
> 2.26.2
>
--
Filipe David Manana,
“Whether you think you can, or you think you can't — you're right.”
next prev parent reply other threads:[~2020-11-09 10:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 21:27 [PATCH 0/8] Locking cleanups and lockdep fix Josef Bacik
2020-11-06 21:27 ` [PATCH 1/8] btrfs: cleanup the locking in btrfs_next_old_leaf Josef Bacik
2020-11-09 10:06 ` Filipe Manana
2020-11-06 21:27 ` [PATCH 2/8] btrfs: unlock to current level " Josef Bacik
2020-11-09 10:12 ` Filipe Manana
2020-11-06 21:27 ` [PATCH 3/8] btrfs: kill path->recurse Josef Bacik
2020-11-09 10:19 ` Filipe Manana
2020-11-06 21:27 ` [PATCH 4/8] btrfs: remove the recursion handling code in locking.c Josef Bacik
2020-11-09 10:20 ` Filipe Manana [this message]
2020-11-11 14:14 ` David Sterba
2020-11-11 14:29 ` David Sterba
2020-11-11 14:43 ` Josef Bacik
2020-11-11 14:59 ` David Sterba
2020-11-06 21:27 ` [PATCH 5/8] btrfs: remove __btrfs_read_lock_root_node Josef Bacik
2020-11-09 10:20 ` Filipe Manana
2020-11-06 21:27 ` [PATCH 6/8] btrfs: use btrfs_tree_read_lock in btrfs_search_slot Josef Bacik
2020-11-09 10:21 ` Filipe Manana
2020-11-06 21:27 ` [PATCH 7/8] btrfs: remove the recurse parameter from __btrfs_tree_read_lock Josef Bacik
2020-11-09 10:22 ` Filipe Manana
2020-11-06 21:27 ` [PATCH 8/8] btrfs: remove ->recursed from extent_buffer Josef Bacik
2020-11-09 10:23 ` Filipe Manana
2020-11-12 18:18 ` [PATCH 0/8] Locking cleanups and lockdep fix 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=CAL3q7H79FhNTbndm+R63H0EzvuuRpjfkaFWs59HdLT6+U0TNYA@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.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 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).