From: Josef Bacik <josef@toxicpanda.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: Use btrfs_transaction::pinned_extents
Date: Fri, 24 Jan 2020 08:51:00 -0500 [thread overview]
Message-ID: <7b0cd11e-b001-02b8-a4d3-b592d9924f5e@toxicpanda.com> (raw)
In-Reply-To: <20200124103541.6415-1-nborisov@suse.com>
On 1/24/20 5:35 AM, Nikolay Borisov wrote:
> This commit flips the switch to start tracking/processing pinned
> extents on a per-transaction basis. It mostly replaces all references
> from btrfs_fs_info::(pinned_extents|freed_extents[]) to
> btrfs_transaction::pinned_extents. Two notable modifications that
> warrant explicit mention are changing clean_pinned_extents to get a
> reference to the previously running transaction. The other one is
> removal of call to btrfs_destroy_pinned_extent since transactions are
> going to be cleaned in btrfs_cleanup_one_transaction.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> ---
>
> V2:
> * Properly release transaction in clean_pinned_extents [Josef]
> * Only check for EXTENT_UPTODATE in add_new_free_space [Josef]
>
> fs/btrfs/block-group.c | 43 +++++++++++++++++++++++-------------
> fs/btrfs/ctree.h | 4 ++--
> fs/btrfs/disk-io.c | 30 +++++--------------------
> fs/btrfs/extent-io-tree.h | 3 +--
> fs/btrfs/extent-tree.c | 31 +++++++-------------------
> fs/btrfs/free-space-cache.c | 2 +-
> fs/btrfs/tests/btrfs-tests.c | 7 ++----
> fs/btrfs/transaction.c | 1 +
> fs/btrfs/transaction.h | 1 +
> include/trace/events/btrfs.h | 3 +--
> 10 files changed, 50 insertions(+), 75 deletions(-)
>
> diff --git a/fs/btrfs/block-group.c b/fs/btrfs/block-group.c
> index 48bb9e08f2e8..91054c32d88a 100644
> --- a/fs/btrfs/block-group.c
> +++ b/fs/btrfs/block-group.c
> @@ -460,10 +460,9 @@ u64 add_new_free_space(struct btrfs_block_group *block_group, u64 start, u64 end
> int ret;
>
> while (start < end) {
> - ret = find_first_extent_bit(info->pinned_extents, start,
> + ret = find_first_extent_bit(&info->excluded_extents, start,
> &extent_start, &extent_end,
> - EXTENT_DIRTY | EXTENT_UPTODATE,
> - NULL);
> + EXTENT_UPTODATE, NULL);
> if (ret)
> break;
>
> @@ -1233,32 +1232,46 @@ static int inc_block_group_ro(struct btrfs_block_group *cache, int force)
> return ret;
> }
>
> -static bool clean_pinned_extents(struct btrfs_block_group *bg)
> +static bool clean_pinned_extents(struct btrfs_trans_handle *trans,
> + struct btrfs_block_group *bg)
> {
> struct btrfs_fs_info *fs_info = bg->fs_info;
> + struct btrfs_transaction *prev_trans = NULL;
> u64 start = bg->start;
> u64 end = start + bg->length - 1;
> int ret;
>
> + spin_lock(&fs_info->trans_lock);
> + if (trans->transaction->list.prev != &fs_info->trans_list) {
> + prev_trans = list_entry(trans->transaction->list.prev,
> + struct btrfs_transaction, list);
> + refcount_inc(&prev_trans->use_count);
> + }
> + spin_unlock(&fs_info->trans_lock);
> +
> /*
> * Hold the unused_bg_unpin_mutex lock to avoid racing with
> * btrfs_finish_extent_commit(). If we are at transaction N,
> * another task might be running finish_extent_commit() for the
> * previous transaction N - 1, and have seen a range belonging
> - * to the block group in freed_extents[] before we were able to
> - * clear the whole block group range from freed_extents[]. This
> + * to the block group in pinned_extents before we were able to
> + * clear the whole block group range from pinned_extents. This
> * means that task can lookup for the block group after we
> - * unpinned it from freed_extents[] and removed it, leading to
> + * unpinned it from pinned_extents[] and removed it, leading to
> * a BUG_ON() at unpin_extent_range().
> */
> mutex_lock(&fs_info->unused_bg_unpin_mutex);
> - ret = clear_extent_bits(&fs_info->freed_extents[0], start, end,
> - EXTENT_DIRTY);
> - if (ret)
> - goto failure;
> + if (prev_trans) {
> + ret = clear_extent_bits(&prev_trans->pinned_extents, start, end,
> + EXTENT_DIRTY);
> + if (ret)
> + goto failure;
> + }
> +
> + btrfs_put_transaction(prev_trans);
The failure case is missing the put. Thanks,
Josef
next prev parent reply other threads:[~2020-01-24 13:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 14:09 [PATCH 00/11] Make pinned extents tracking per-transaction Nikolay Borisov
2020-01-20 14:09 ` [PATCH 01/11] btrfs: Perform pinned cleanup directly in btrfs_destroy_delayed_refs Nikolay Borisov
2020-01-21 14:22 ` Josef Bacik
2020-01-30 13:51 ` David Sterba
2020-02-05 8:32 ` Nikolay Borisov
2020-01-20 14:09 ` [PATCH 02/11] btrfs: Make btrfs_pin_extent take trans handle Nikolay Borisov
2020-01-21 14:23 ` Josef Bacik
2020-01-20 14:09 ` [PATCH 03/11] btrfs: Introduce unaccount_log_buffer Nikolay Borisov
2020-01-22 20:04 ` Josef Bacik
2020-01-20 14:09 ` [PATCH 04/11] btrfs: Call btrfs_pin_reserved_extent only during active transaction Nikolay Borisov
2020-01-22 20:05 ` Josef Bacik
2020-01-20 14:09 ` [PATCH 05/11] btrfs: Make btrfs_pin_reserved_extent take transaction Nikolay Borisov
2020-01-22 20:06 ` Josef Bacik
2020-01-20 14:09 ` [PATCH 06/11] btrfs: Make btrfs_pin_extent_for_log_replay take transaction handle Nikolay Borisov
2020-01-22 20:06 ` Josef Bacik
2020-01-20 14:09 ` [PATCH 07/11] btrfs: Make pin_down_extent take btrfs_trans_handle Nikolay Borisov
2020-01-22 20:07 ` Josef Bacik
2020-01-20 14:09 ` [PATCH 08/11] btrfs: Pass trans handle to write_pinned_extent_entries Nikolay Borisov
2020-01-22 20:07 ` Josef Bacik
2020-01-20 14:09 ` [PATCH 09/11] btrfs: Mark pinned log extents as excluded Nikolay Borisov
2020-01-22 20:12 ` Josef Bacik
2020-01-30 13:53 ` David Sterba
2020-01-30 14:03 ` Nikolay Borisov
2020-02-05 8:51 ` Nikolay Borisov
2020-01-20 14:09 ` [PATCH 10/11] btrfs: Factor out pinned extent clean up in btrfs_delete_unused_bgs Nikolay Borisov
2020-01-22 20:14 ` Josef Bacik
2020-01-20 14:09 ` [PATCH 11/11] btrfs: Use btrfs_transaction::pinned_extents Nikolay Borisov
2020-01-22 20:21 ` Josef Bacik
2020-01-23 8:54 ` Nikolay Borisov
2020-01-23 13:40 ` Josef Bacik
2020-01-24 10:35 ` [PATCH v2] " Nikolay Borisov
2020-01-24 13:51 ` Josef Bacik [this message]
2020-01-24 15:18 ` [PATCH v3] " Nikolay Borisov
2020-01-24 15:27 ` Josef Bacik
2020-01-30 14:02 ` David Sterba
2020-02-06 18:10 ` [PATCH 11/11 " David Sterba
2020-02-06 19:40 ` Nikolay Borisov
2020-02-14 15:33 ` David Sterba
2020-02-06 19:59 ` [PATCH 00/11] Make pinned extents tracking per-transaction 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=7b0cd11e-b001-02b8-a4d3-b592d9924f5e@toxicpanda.com \
--to=josef@toxicpanda.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).