From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH v3 0/6] Compress path cleanups
Date: Thu, 21 Feb 2019 13:57:11 +0200 [thread overview]
Message-ID: <20190221115717.5128-1-nborisov@suse.com> (raw)
Another day, another revision, hopefully this is the last one.
Changes since v2:
* Reworked patch 1 and made async_cow be the top-level context struct and each
chunk is tracked by async_chunk. This cleansup the pointer gymnastics I was
doing in the previous version (Johannes)
* Reworded changelogs in various patches to reflect the usage of async_chunk.
* Fixed changelog in patch2 to properly reflect fs_info is referenced from
btrfs_work (Johannes)
* Added Reviwed-by to patches 4/5/6
Changes since v1:
* Fixed error handling in patch 1 - now properly cleanup on failure.
* Fixed subject of patch 3
* Added patches 4/5 as minor cleanups to the code.
Nikolay Borisov (6):
btrfs: Refactor cow_file_range_async
btrfs: Remove fs_info from struct async_chunk
btrfs: Make compress_file_range take only struct async_chunk
btrfs: Replace clear_extent_bit with unlock_extent
btrfs: Set iotree only once in submit_compressed_extents
btrfs: Factor out common extent locking code in
submit_compressed_extents
fs/btrfs/inode.c | 148 +++++++++++++++++++++++++++--------------------
1 file changed, 84 insertions(+), 64 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-21 11:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 11:57 Nikolay Borisov [this message]
2019-02-21 11:57 ` [PATCH v3 1/6] btrfs: Refactor cow_file_range_async Nikolay Borisov
2019-02-21 13:15 ` Johannes Thumshirn
2019-02-21 13:25 ` Nikolay Borisov
2019-02-21 15:07 ` Johannes Thumshirn
2019-02-21 15:09 ` Nikolay Borisov
2019-02-22 18:05 ` David Sterba
2019-02-22 18:13 ` David Sterba
2019-02-21 11:57 ` [PATCH v3 2/6] btrfs: Remove fs_info from struct async_chunk Nikolay Borisov
2019-02-21 13:07 ` Johannes Thumshirn
2019-02-21 11:57 ` [PATCH v3 3/6] btrfs: Make compress_file_range take only " Nikolay Borisov
2019-02-21 13:07 ` Johannes Thumshirn
2019-02-21 11:57 ` [PATCH v3 4/6] btrfs: Replace clear_extent_bit with unlock_extent Nikolay Borisov
2019-02-21 11:57 ` [PATCH v3 5/6] btrfs: Set iotree only once in submit_compressed_extents Nikolay Borisov
2019-02-21 11:57 ` [PATCH v3 6/6] btrfs: Factor out common extent locking code " 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=20190221115717.5128-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).