From: Timofey Titovets <nefelim4ag@gmail.com>
To: dsterba@suse.cz, Timofey Titovets <nefelim4ag@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v5 2/2] Btrfs: compression must free at least one sector size
Date: Mon, 5 Jun 2017 21:56:14 +0300 [thread overview]
Message-ID: <CAGqmi76jA2YmchTrQkMUFPfbXEtDXMs9C3Ji7v7kN_vtffAP_Q@mail.gmail.com> (raw)
In-Reply-To: <20170605161003.GX12135@twin.jikos.cz>
2017-06-05 19:10 GMT+03:00 David Sterba <dsterba@suse.cz>:
> On Tue, May 30, 2017 at 02:18:05AM +0300, Timofey Titovets wrote:
>> Btrfs already skip store of data where compression didn't
>> free at least one byte. Let's make logic better and make check
>> that compression free at least one sector size
>> because in another case it useless to store this data compressed
>>
>> Signed-off-by: Timofey Titovets <nefelim4ag@gmail.com>
>> ---
>> fs/btrfs/inode.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
>> index 17cbe930..2793007b 100644
>> --- a/fs/btrfs/inode.c
>> +++ b/fs/btrfs/inode.c
>> @@ -609,9 +609,10 @@ static noinline void compress_file_range(struct inode *inode,
>> /*
>> * one last check to make sure the compression is really a
>> * win, compare the page count read with the blocks on disk
>> + * compression must free at least one sector size
>> */
>> total_in = ALIGN(total_in, PAGE_SIZE);
>> - if (total_compressed >= total_in) {
>> + if (total_compressed + blocksize > total_in) {
>
> We're doing aligned calculation here, shouldn't this be >= ?
>
> If total_compressed + blocksize == total_in, we have saved exactly one
> blocksize.
We discussed that already in:
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg64350.html
IIRC: long in short:
- input data size 8192
- output data size 4096
This invertion logic, i.e. check if compression can be skipped, if
comparasion are true -> skip compression.
In case of above check,
old logic:
total_compressed >= total_in
4096 >= 8192 -> will_compress=1
With if blocksize added:
4096+4096 >= 8192 -> will_compress=0
So this must be changed to:
4096+4096 > 8192 -> will_compress=1
Because compression save one blocksize
Also will_compress not used after this code, so in theory this code
can be refactored to be more obvious, like that:
total_in = ALIGN(total_in, PAGE_SIZE);
- if (total_compressed + blocksize > total_in) {
- will_compress = 0;
- } else {
+ if (total_compressed + blocksize <= total_in) {
num_bytes = total_in;
*num_added += 1;
Thanks
--
Have a nice day,
Timofey.
next prev parent reply other threads:[~2017-06-05 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 23:18 [PATCH v5 0/2] Btrfs: compression fixes Timofey Titovets
2017-05-29 23:18 ` [PATCH v5 1/2] Btrfs: lzo.c - compressed data size must be less then input size Timofey Titovets
2017-06-05 15:59 ` David Sterba
2017-05-29 23:18 ` [PATCH v5 2/2] Btrfs: compression must free at least one sector size Timofey Titovets
2017-06-05 16:10 ` David Sterba
2017-06-05 18:56 ` Timofey Titovets [this message]
2017-06-06 11:22 ` 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=CAGqmi76jA2YmchTrQkMUFPfbXEtDXMs9C3Ji7v7kN_vtffAP_Q@mail.gmail.com \
--to=nefelim4ag@gmail.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).