From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] Add full support for cloning ranges with inline extents
Date: Wed, 19 Feb 2020 14:05:39 +0000 [thread overview]
Message-ID: <20200219140539.1641457-1-fdmanana@kernel.org> (raw)
From: Filipe Manana <fdmanana@suse.com>
This patchset adds support for currently unsupported cases of reflink
operations that cover a file range that has inline extents, more details
on why/how in patch 4/4.
It also starts by moving all the reflink code out of ioctl.c into a new
file named reflink.c (like xfs does) since this code is quite significant
in size and has grown over the years.
Filipe Manana (4):
Btrfs: move all reflink implementation code into its own file
Btrfs: simplify inline extent handling when doing reflinks
Btrfs: resurrect extent_read_full_page_nolock()
Btrfs: implement full reflink support for inline extents
fs/btrfs/Makefile | 2 +-
fs/btrfs/compression.c | 8 +-
fs/btrfs/ctree.h | 2 +
fs/btrfs/extent_io.c | 47 ++-
fs/btrfs/extent_io.h | 3 +
fs/btrfs/ioctl.c | 733 -------------------------------------
fs/btrfs/reflink.c | 803 +++++++++++++++++++++++++++++++++++++++++
7 files changed, 854 insertions(+), 744 deletions(-)
create mode 100644 fs/btrfs/reflink.c
--
2.25.0
reply other threads:[~2020-02-19 14:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200219140539.1641457-1-fdmanana@kernel.org \
--to=fdmanana@kernel.org \
--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).