From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 10/12] btrfs: Optimize unallocated chunks discard
Date: Mon, 25 Mar 2019 17:29:36 +0100 [thread overview]
Message-ID: <20190325162935.GJ10640@twin.jikos.cz> (raw)
In-Reply-To: <20190325123132.27835-11-nborisov@suse.com>
On Mon, Mar 25, 2019 at 02:31:30PM +0200, Nikolay Borisov wrote:
> Currently unallocated chunks are always trimmed. For example
> 2 consecutive trims on large storage would trim freespace twice
> irrespective of whether the space was actually allocated or not between
> those trims.
>
> Optimise this behavior by exploiting the newly introduced alloc_state
> tree of btrfs_device. A new CHUNK_TRIMMED bit is used to mark
> those unallocated chunks which have been trimmed and have not been
> allocated afterwards. On chunk allocation the respective underlying devices'
> physical space will have its CHUNK_TRIMMED flag cleared. This avoids
> submitting discards for space which hasn't been changed since the last
> time discard was issued.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> ---
> fs/btrfs/extent-tree.c | 57 +++++++++++++++++++++++++++++++++++++++++-
> fs/btrfs/extent_io.h | 8 +++++-
> fs/btrfs/extent_map.c | 4 ++-
> 3 files changed, 66 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 574c73e0a7c0..503d68ba3f6a 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -11249,6 +11249,54 @@ int btrfs_error_unpin_extent_range(struct btrfs_fs_info *fs_info,
> return unpin_extent_range(fs_info, start, end, false);
> }
>
> +static bool should_skip_trim(struct btrfs_device *device, u64 *start, u64 *len)
> +{
> + u64 trimmed_start = 0, trimmed_end = 0;
> + u64 end = *start + *len - 1;
> +
> + if (!find_first_extent_bit(&device->alloc_state, *start, &trimmed_start,
> + &trimmed_end, CHUNK_TRIMMED, NULL)) {
> + u64 trimmed_len = trimmed_end - trimmed_start + 1;
> +
> + if (*start < trimmed_start) {
> + if (in_range(end, trimmed_start, trimmed_len) ||
> + end > trimmed_end) {
> + /*
> + * start|------|end
> + * ts|--|trimmed_len
> + * OR
> + * start|-----|end
> + * ts|-----|trimmed_len
> + */
> + *len = trimmed_start - *start;
> + return false;
> + } else if (end < trimmed_start) {
> + /*
> + * start|------|end
> + * ts|--|trimmed_len
> + */
> + return false;
> + }
> + } else if (in_range(*start, trimmed_start, trimmed_len)) {
> + if (in_range(end, trimmed_start, trimmed_len)) {
> + /*
> + * start|------|end
> + * ts|----------|trimmed_len
> + */
> + return true;
> + } else {
> + /*
> + * start|-----------|end
> + * ts|----------|trimmed_len
> + */
> + *start = trimmed_end + 1;
> + *len = end - *start + 1;
> + return false;
> + }
> + }
> + }
> + return false;
> +}
> /*
> * It used to be that old block groups would be left around forever.
> * Iterating over them would be enough to trim unused space. Since we
> @@ -11319,7 +11367,14 @@ static int btrfs_trim_free_extents(struct btrfs_device *device,
> start = max(range->start, start);
> len = min(range->len, len);
>
> - ret = btrfs_issue_discard(device->bdev, start, len, &bytes);
> + if (!should_skip_trim(device, &start, &len)) {
> + ret = btrfs_issue_discard(device->bdev, start, len,
> + &bytes);
> + if (!ret)
> + set_extent_bits(&device->alloc_state, start,
> + start + bytes - 1,
> + CHUNK_TRIMMED);
> + }
> mutex_unlock(&fs_info->chunk_mutex);
>
> if (ret)
> diff --git a/fs/btrfs/extent_io.h b/fs/btrfs/extent_io.h
> index 4bcc203b5431..9dd5190d9dd8 100644
> --- a/fs/btrfs/extent_io.h
> +++ b/fs/btrfs/extent_io.h
> @@ -28,8 +28,14 @@
> #define EXTENT_CTLBITS (EXTENT_DO_ACCOUNTING)
>
>
> -/* Redefined bits above which are used only in the device allocation tree */
> +/*
> + * Redefined bits above which are used only in the device allocation tree,
> + * shouldn't be using EXTENT_IOBITS(EXTENT_LOCKED/EXTENT_WRITEBACK) /
> + * EXTENT_BOUNDARY / EXTENT_CLEAR_META_RESV / EXTENT_CLEAR_DATA_RESV because
Fixup after recent changes in misc-net: EXTENT_IOBITS and EXTENT_WRITEBACK
are gone, comment updated.
> + * they have special meaning to the bit manipulation functions
> + */
> #define CHUNK_ALLOCATED EXTENT_DIRTY
> +#define CHUNK_TRIMMED EXTENT_DEFRAG
>
> /*
> * flags for bio submission. The high bits indicate the compression
> diff --git a/fs/btrfs/extent_map.c b/fs/btrfs/extent_map.c
> index 0820f6fcf3a6..9e8c0904f623 100644
> --- a/fs/btrfs/extent_map.c
> +++ b/fs/btrfs/extent_map.c
> @@ -389,8 +389,10 @@ int add_extent_mapping(struct extent_map_tree *tree,
> goto out;
>
> setup_extent_mapping(tree, em, modified);
> - if (test_bit(EXTENT_FLAG_FS_MAPPING, &em->flags))
> + if (test_bit(EXTENT_FLAG_FS_MAPPING, &em->flags)) {
> extent_map_device_set_bits(em, CHUNK_ALLOCATED);
> + extent_map_device_clear_bits(em, CHUNK_TRIMMED);
> + }
> out:
> return ret;
> }
> --
> 2.17.1
next prev parent reply other threads:[~2019-03-25 16:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 12:31 [PATCH v3 00/12] FITRIM improvements Nikolay Borisov
2019-03-25 12:31 ` [PATCH v3 01/12] btrfs: Honour FITRIM range constraints during free space trim Nikolay Borisov
2019-03-25 12:31 ` [PATCH v3 02/12] btrfs: combine device update operations during transaction commit Nikolay Borisov
2019-03-25 13:44 ` Nikolay Borisov
2019-03-25 12:31 ` [PATCH v3 03/12] btrfs: Handle pending/pinned chunks before blockgroup relocation during device shrink Nikolay Borisov
2019-03-25 15:09 ` David Sterba
2019-03-25 15:16 ` David Sterba
2019-03-25 12:31 ` [PATCH v3 04/12] btrfs: Rename and export clear_btree_io_tree Nikolay Borisov
2019-03-25 12:31 ` [PATCH v3 05/12] btrfs: Populate ->orig_block_len during read_one_chunk Nikolay Borisov
2019-03-25 12:31 ` [PATCH v3 06/12] btrfs: Introduce new bits for device allocation tree Nikolay Borisov
2019-03-25 16:12 ` David Sterba
2019-03-25 16:13 ` Nikolay Borisov
2019-03-25 12:31 ` [PATCH v3 07/12] btrfs: replace pending/pinned chunks lists with io tree Nikolay Borisov
2019-03-25 14:22 ` David Sterba
2019-03-25 16:26 ` David Sterba
2019-03-25 16:43 ` Nikolay Borisov
2019-03-25 16:57 ` David Sterba
2019-03-25 12:31 ` [PATCH v3 08/12] btrfs: Remove 'trans' argument from find_free_dev_extent(_start) Nikolay Borisov
2019-03-25 12:31 ` [PATCH v3 09/12] btrfs: Factor out in_range macro Nikolay Borisov
2019-03-25 12:31 ` [PATCH v3 10/12] btrfs: Optimize unallocated chunks discard Nikolay Borisov
2019-03-25 16:29 ` David Sterba [this message]
2019-03-25 12:31 ` [PATCH v3 11/12] btrfs: Implement find_first_clear_extent_bit Nikolay Borisov
2019-03-25 12:31 ` [PATCH v3 12/12] btrfs: Switch btrfs_trim_free_extents to find_first_clear_extent_bit Nikolay Borisov
2019-03-25 18:44 ` [PATCH v3 00/12] FITRIM improvements Darrick J. Wong
2019-03-26 8:09 ` Nikolay Borisov
2019-03-26 10:50 ` Filipe Manana
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=20190325162935.GJ10640@twin.jikos.cz \
--to=dsterba@suse.cz \
--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