linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: make use of inode_need_compress()
Date: Thu, 20 Jul 2017 10:22:13 +0800	[thread overview]
Message-ID: <e48652eb-78bb-d6b7-4bbf-3722f0af2fb7@oracle.com> (raw)
In-Reply-To: <20170718150125.GT2866@twin.jikos.cz>



On 07/18/2017 11:01 PM, David Sterba wrote:
> On Tue, Jul 18, 2017 at 05:37:47PM +0800, Anand Jain wrote:
>> Its better to have the policy enforcement going through a function,
>> so that we have better control and visibility of the decision logic.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>>   fs/btrfs/inode.c | 7 +++----
>>   1 file changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
>> index 06dea7c89bbd..d0cc3de120b7 100644
>> --- a/fs/btrfs/inode.c
>> +++ b/fs/btrfs/inode.c
>> @@ -1189,11 +1189,10 @@ static int cow_file_range_async(struct inode *inode, struct page *locked_page,
>>   		async_cow->locked_page = locked_page;
>>   		async_cow->start = start;
>>   
>> -		if (BTRFS_I(inode)->flags & BTRFS_INODE_NOCOMPRESS &&
>> -		    !btrfs_test_opt(fs_info, FORCE_COMPRESS))
>> -			cur_end = end;
>> -		else
>> +		if (inode_need_compress(inode))
>>   			cur_end = min(end, start + SZ_512K - 1);
>> +		else
>> +			cur_end = end;
> 
> The opencoded test should be cleaned up, however cow_file_range_async is
> called from run_delalloc_range if the inode_need_compress passes the
> 'inode_need_compress' condition. So at minimum, checking again here is
> redundant,

  David, no its not redundant. If the preceding SZ_512K block is not
  compressible, then we would have already set the BTRFS_INODE_NOCOMPRESS
  flag, which then we would straightaway go up to the end.

> but we still might need to know if the compression is
> desired.
  Uh ?

> The check does no depend on anything inside the loop, so it should be
> moved out of it. 

  No, it should not be, if you move check outside then it will act as if
  compress-force is set even if you don't set it.

> If I understand the logic correctly, we get to
> cow_file_range_async and always want to compress, so the test should be
> dropped entirely.

  sorry. its wrong. as above.



  reply	other threads:[~2017-07-20  2:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18  9:37 [PATCH] btrfs: make use of inode_need_compress() Anand Jain
2017-07-18 15:01 ` David Sterba
2017-07-20  2:22   ` Anand Jain [this message]
2017-07-21 18: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=e48652eb-78bb-d6b7-4bbf-3722f0af2fb7@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --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).