From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Merge inode_can_compress in inode_need_compress
Date: Tue, 18 Aug 2020 15:50:58 +0800 [thread overview]
Message-ID: <662ce31b-7996-0a96-85d1-3872afa452e8@gmx.com> (raw)
In-Reply-To: <20200818063056.9094-1-nborisov@suse.com>
On 2020/8/18 下午2:30, Nikolay Borisov wrote:
> The latter is the only caller of the former. Just open code can_compress
> into need_compress and also remove the warning since it's made redundant
> by this change.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> fs/btrfs/inode.c | 21 +++------------------
> 1 file changed, 3 insertions(+), 18 deletions(-)
>
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index 15dc8b6871ac..19e1918bad5c 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -410,17 +410,6 @@ static noinline int add_async_extent(struct async_chunk *cow,
> return 0;
> }
>
> -/*
> - * Check if the inode has flags compatible with compression
> - */
> -static inline bool inode_can_compress(struct btrfs_inode *inode)
> -{
> - if (inode->flags & BTRFS_INODE_NODATACOW ||
> - inode->flags & BTRFS_INODE_NODATASUM)
> - return false;
> - return true;
> -}
> -
> /*
> * Check if the inode needs to be submitted to compression, based on mount
> * options, defragmentation, properties or heuristics.
> @@ -430,12 +419,9 @@ static inline int inode_need_compress(struct btrfs_inode *inode, u64 start,
> {
> struct btrfs_fs_info *fs_info = inode->root->fs_info;
>
> - if (!inode_can_compress(inode)) {
> - WARN(IS_ENABLED(CONFIG_BTRFS_DEBUG),
> - KERN_ERR "BTRFS: unexpected compression for ino %llu\n",
> - btrfs_ino(inode));
> + if (inode->flags & BTRFS_INODE_NODATACOW ||
> + inode->flags & BTRFS_INODE_NODATASUM)
> return 0;
> - }
> /* force compress */
> if (btrfs_test_opt(fs_info, FORCE_COMPRESS))
> return 1;
> @@ -1833,8 +1819,7 @@ int btrfs_run_delalloc_range(struct btrfs_inode *inode, struct page *locked_page
> } else if (inode->flags & BTRFS_INODE_PREALLOC && !force_cow) {
> ret = run_delalloc_nocow(inode, locked_page, start, end,
> page_started, 0, nr_written);
> - } else if (!inode_can_compress(inode) ||
> - !inode_need_compress(inode, start, end)) {
> + } else if (!inode_need_compress(inode, start, end)) {
> ret = cow_file_range(inode, locked_page, start, end,
> page_started, nr_written, 1);
> } else {
>
next prev parent reply other threads:[~2020-08-18 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 6:30 [PATCH] btrfs: Merge inode_can_compress in inode_need_compress Nikolay Borisov
2020-08-18 7:50 ` Qu Wenruo [this message]
2020-08-26 11:13 ` David Sterba
2020-08-31 20:40 ` David Sterba
2020-08-31 20:44 ` 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=662ce31b-7996-0a96-85d1-3872afa452e8@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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