From: Nikolay Borisov <nborisov@suse.com>
To: Ethan Lien <ethanlien@synology.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Skip some btrfs_cross_ref_exist() check in nocow path
Date: Wed, 16 May 2018 11:31:09 +0300 [thread overview]
Message-ID: <1fa48d67-813e-c909-93a8-830fc1c3391f@suse.com> (raw)
In-Reply-To: <20180516082854.29254-1-ethanlien@synology.com>
On 16.05.2018 11:28, Ethan Lien wrote:
> In nocow path, we check if the extent is snapshotted in
> btrfs_cross_ref_exist(). We can do the similar check earlier and avoid
> unnecessary search into extent tree.
>
> Signed-off-by: Ethan Lien <ethanlien@synology.com>
If this is supposed to be a performance improvement do you have any
measurements that prove that this is indeed the case?
> ---
> fs/btrfs/inode.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index d241285a0d2a..96927f2ccd4b 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -1373,6 +1373,9 @@ static noinline int run_delalloc_nocow(struct inode *inode,
> btrfs_file_extent_encryption(leaf, fi) ||
> btrfs_file_extent_other_encoding(leaf, fi))
> goto out_check;
> + if (btrfs_file_extent_generation(leaf, fi) <=
> + btrfs_root_last_snapshot(&root->root_item))
> + goto out_check;
> if (extent_type == BTRFS_FILE_EXTENT_REG && !force)
> goto out_check;
> if (btrfs_extent_readonly(fs_info, disk_bytenr))
> @@ -7368,6 +7371,10 @@ noinline int can_nocow_extent(struct inode *inode, u64 offset, u64 *len,
> btrfs_file_extent_other_encoding(leaf, fi))
> goto out;
>
> + if (btrfs_file_extent_generation(leaf, fi) <=
> + btrfs_root_last_snapshot(&root->root_item))
> + goto out;
> +
> backref_offset = btrfs_file_extent_offset(leaf, fi);
>
> if (orig_start) {
>
next prev parent reply other threads:[~2018-05-16 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 8:28 [PATCH] btrfs: Skip some btrfs_cross_ref_exist() check in nocow path Ethan Lien
2018-05-16 8:31 ` Nikolay Borisov [this message]
2018-05-16 15:11 ` David Sterba
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=1fa48d67-813e-c909-93a8-830fc1c3391f@suse.com \
--to=nborisov@suse.com \
--cc=ethanlien@synology.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).