From: Timofey Titovets <nefelim4ag@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Timofey Titovets <nefelim4ag@gmail.com>
Subject: [PATCH 0/1] Btrfs: populate heuristic with logic
Date: Thu, 5 Oct 2017 13:07:25 +0300 [thread overview]
Message-ID: <20171005100726.16438-1-nefelim4ag@gmail.com> (raw)
As core part of heuristic merged to for-next tree,
I send another patch with shannon entropy calculation,
as that metric will cover another part of cases.
That also will cover most of silesia corpus data.
P.S.
i reverse ported it, so:
https://github.com/Nefelim4ag/companalyze
For now that only for guess kernel counters for specific data,
i.e. no policy logic. Only RAW counters.
To know if tunning needed on specific data case and easy check
that heuristic see for that data.
Timofey Titovets (1):
Btrfs: heuristic add shannon entropy calculation
fs/btrfs/compression.c | 314 ++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 313 insertions(+), 1 deletion(-)
--
2.14.2
next reply other threads:[~2017-10-05 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 10:07 Timofey Titovets [this message]
2017-10-05 10:07 ` [PATCH 1/1] Btrfs: heuristic add shannon entropy calculation Timofey Titovets
2017-10-06 18:24 ` David Sterba
2017-10-07 0:08 ` Timofey Titovets
2017-10-09 15:43 ` 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=20171005100726.16438-1-nefelim4ag@gmail.com \
--to=nefelim4ag@gmail.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).