From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH v2 00/12] FITRIM improvements
Date: Mon, 11 Feb 2019 10:34:58 +0200 [thread overview]
Message-ID: <20190211083510.27591-1-nborisov@suse.com> (raw)
Here is the second version of the FITRIM patchset. For background information
consult the previous [0] post. Changes since v1:
* Dropped some cleanup patches as they have been merged in the meantime.
* In Patch 2 switched list iteration to list_for_each_entry_safe in
btrfs_cleanup_one_transaction. (Johanness Thumshirn)
* Fixed a bug in Patch 12 which leads to infinite loop. Now find_first_clear_bit
returns void since it doesn't have enough context to tell whether it exhausted
the search space
* Fixed kerneldoc format in Patch 11 (Johaness Thumshirn)
* Rebased on latest misc-next branch
* Further testing of the patchset with newly enabled shared/298 test - succeeds.
[0] https://lore.kernel.org/linux-btrfs/20190130145102.4708-1-nborisov@suse.com/
Jeff Mahoney (2):
btrfs: combine device update operations during transaction commit
btrfs: replace pending/pinned chunks lists with io tree
Nikolay Borisov (10):
btrfs: Honour FITRIM range constraints during free space trim
btrfs: Handle pending/pinned chunks before blockgroup relocation
during device shrink
btrfs: Rename and export clear_btree_io_tree
btrfs: Populate ->orig_block_len during read_one_chunk
btrfs: Introduce new bits for device allocation tree
btrfs: Remove 'trans' argument from find_free_dev_extent(_start)
btrfs: Factor out in_range macro
btrfs: Optimize unallocated chunks discard
btrfs: Implement find_first_clear_extent_bit
btrfs: Switch btrfs_trim_free_extents to find_first_clear_extent_bit
fs/btrfs/ctree.h | 8 +-
fs/btrfs/dev-replace.c | 2 +-
fs/btrfs/disk-io.c | 18 +--
fs/btrfs/extent-tree.c | 102 +++++--------
fs/btrfs/extent_io.c | 103 +++++++++++++-
fs/btrfs/extent_io.h | 19 ++-
fs/btrfs/extent_map.c | 38 +++++
fs/btrfs/extent_map.h | 1 -
fs/btrfs/free-space-cache.c | 4 -
fs/btrfs/transaction.c | 53 ++-----
fs/btrfs/transaction.h | 2 +-
fs/btrfs/volumes.c | 277 ++++++++++++++----------------------
fs/btrfs/volumes.h | 23 ++-
13 files changed, 332 insertions(+), 318 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-11 8:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 8:34 Nikolay Borisov [this message]
2019-02-11 8:34 ` [PATCH v2 01/12] btrfs: Honour FITRIM range constraints during free space trim Nikolay Borisov
2019-02-11 8:35 ` [PATCH v2 02/12] btrfs: combine device update operations during transaction commit Nikolay Borisov
2019-02-28 16:52 ` David Sterba
2019-02-11 8:35 ` [PATCH v2 03/12] btrfs: Handle pending/pinned chunks before blockgroup relocation during device shrink Nikolay Borisov
2019-02-11 8:35 ` [PATCH v2 04/12] btrfs: Rename and export clear_btree_io_tree Nikolay Borisov
2019-02-28 16:53 ` David Sterba
2019-02-11 8:35 ` [PATCH v2 05/12] btrfs: Populate ->orig_block_len during read_one_chunk Nikolay Borisov
2019-02-28 16:53 ` David Sterba
2019-02-11 8:35 ` [PATCH v2 06/12] btrfs: Introduce new bits for device allocation tree Nikolay Borisov
2019-02-28 16:57 ` David Sterba
2019-02-11 8:35 ` [PATCH v2 07/12] btrfs: replace pending/pinned chunks lists with io tree Nikolay Borisov
2019-02-12 14:13 ` [PATCH] btrfs: Transpose btrfs_close_devices/btrfs_mapping_tree_free in close_ctree Nikolay Borisov
2019-02-11 8:35 ` [PATCH v2 08/12] btrfs: Remove 'trans' argument from find_free_dev_extent(_start) Nikolay Borisov
2019-02-11 8:35 ` [PATCH v2 09/12] btrfs: Factor out in_range macro Nikolay Borisov
2019-02-28 18:00 ` David Sterba
2019-02-11 8:35 ` [PATCH v2 10/12] btrfs: Optimize unallocated chunks discard Nikolay Borisov
2019-02-11 8:35 ` [PATCH v2 11/12] btrfs: Implement find_first_clear_extent_bit Nikolay Borisov
2019-02-11 8:35 ` [PATCH v2 12/12] btrfs: Switch btrfs_trim_free_extents to find_first_clear_extent_bit Nikolay Borisov
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=20190211083510.27591-1-nborisov@suse.com \
--to=nborisov@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 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).