From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, Adam Borowski <kilobyte@angband.pl>,
Roman Mamedov <rm@romanrm.net>,
Timofey Titovets <nefelim4ag@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] Btrfs: add skeleton code for compression heuristic
Date: Mon, 24 Jul 2017 23:40:17 +0800 [thread overview]
Message-ID: <950a249d-9fb2-103a-0101-d37e6609ba8f@oracle.com> (raw)
In-Reply-To: <20170724145356.GX2866@twin.jikos.cz>
> Eg. files that are already compressed would increase the cpu consumption
> with compress-force, while they'd be hopefully detected as
> incompressible with 'compress' and clever heuristics. So the NOCOMPRESS
> bit would better reflect the status of the file.
current NOCOMPRESS is based on trial and error method and is more
accurate than heuristic also loss of cpu power is only one time ?
May be the only opportunity that heuristic can facilitate is at the
logic to monitor and reset the NOCOMPRESS, as of now there is no
such a logic.
Thanks, Anand
next prev parent reply other threads:[~2017-07-24 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 13:52 [PATCH v3] Btrfs: add skeleton code for compression heuristic Timofey Titovets
2017-07-17 18:30 ` David Sterba
2017-07-21 5:00 ` Anand Jain
2017-07-21 18:37 ` Roman Mamedov
2017-07-21 21:00 ` Adam Borowski
2017-07-22 0:52 ` Anand Jain
2017-07-24 14:53 ` David Sterba
2017-07-24 15:40 ` Anand Jain [this message]
2017-07-27 15:36 ` David Sterba
2017-07-28 14:04 ` Anand Jain
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=950a249d-9fb2-103a-0101-d37e6609ba8f@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=nefelim4ag@gmail.com \
--cc=rm@romanrm.net \
/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).