From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org, josef@toxicpanda.com,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH v2 1/3] Btrfs: move all reflink implementation code into its own file
Date: Fri, 21 Feb 2020 15:37:13 +0100 [thread overview]
Message-ID: <20200221143713.GI2902@twin.jikos.cz> (raw)
In-Reply-To: <20200221110508.2641768-1-fdmanana@kernel.org>
On Fri, Feb 21, 2020 at 11:05:08AM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> The reflink code is quite large and has been living in ioctl.c since ever.
> It has grown over the years after many bug fixes and improvements, and
> since I'm planning on making some further improvements on it, it's time
> to get it better organized by moving into its own file, reflink.c
> (similar to what xfs does for example).
>
> This change only moves the code out of ioctl.c into the new file, it
> doesn't do any other change.
Makes sense.
> --- a/fs/btrfs/ctree.h
> +++ b/fs/btrfs/ctree.h
> @@ -2989,6 +2989,8 @@ int btrfs_dirty_pages(struct inode *inode, struct page **pages,
> size_t num_pages, loff_t pos, size_t write_bytes,
> struct extent_state **cached);
> int btrfs_fdatawrite_range(struct inode *inode, loff_t start, loff_t end);
> +
> +/* reflink.c */
> loff_t btrfs_remap_file_range(struct file *file_in, loff_t pos_in,
> struct file *file_out, loff_t pos_out,
> loff_t len, unsigned int remap_flags);
Let's create reflink.h with all the relevant declarations for reflink
moved out of ctree.h too.
I see only BTRFS_MAX_DEDUPE_LEN and declaration of btrfs_remap_file_range,
that's not much for now but it's cleaner and for future extensions.
Thanks.
prev parent reply other threads:[~2020-02-21 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 11:04 [PATCH v2 0/3] Add full support for cloning inline extents fdmanana
2020-02-21 11:05 ` [PATCH v2 1/3] Btrfs: move all reflink implementation code into its own file fdmanana
2020-02-21 14:37 ` David Sterba [this message]
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=20200221143713.GI2902@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.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