From: Roger Pack <rogerpack2005@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Fwd: lz4 status?
Date: Thu, 14 Aug 2014 07:23:53 -0600 [thread overview]
Message-ID: <CADCGFBW8CiRB7j+jsiLtjuFdku24rvnSkENwv27+aDv0tG9=jQ@mail.gmail.com> (raw)
In-Reply-To: <CADCGFBWSor1oZ7XzqcJZ4-4XwCS-TbMHmBRzezRi01=SRVjpQA@mail.gmail.com>
On Wed, Jul 10, 2013 at 4:54 PM, David Sterba <dsterba@suse.cz> wrote:
>
> On Sun, Jun 30, 2013 at 12:35:09PM -0500, Mitch Harder wrote:
> > There's been a parallel effort to incorporate a general set of lz4
> > patches in the kernel.
> >
> > I see these patches are currently queued up in the linux-next tree, so
> > we may see them in the 3.11 kernel.
>
> The patches are now merged into 3.11.
>
> > It looks like lz4 and lz4hc will be provided.
>
> Regarding HC mode, there are some core compression code changes needed
> in order to fully utilize the its potential, namely larger chunk size
> that's compressed at a time. There was some tiny yet measurable gain of
> HC against ordinary mode compared on current 4k-at-a-time
> implementation, but the space savings did not justify the speed drop of
> HC mode.
>
> I can't say if the patchset will be ready for 3.12 though.
>
> david
Any update here re: lz4 integration?
I noticed some people here saying they saw it not available yet?
http://www.phoronix.com/forums/showthread.php?94912-Btrfs-Gets-Big-Changes-Features-In-Linux-3-14-Kernel
Cheers!
-roger-
next prev parent reply other threads:[~2014-08-14 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 15:57 lz4 status? Roger Pack
2013-06-30 17:35 ` Mitch Harder
2013-07-01 13:27 ` Roger Pack
2013-07-10 22:54 ` David Sterba
2013-07-11 15:21 ` Chris Mason
[not found] ` <CADCGFBWSor1oZ7XzqcJZ4-4XwCS-TbMHmBRzezRi01=SRVjpQA@mail.gmail.com>
2014-08-14 13:23 ` Roger Pack [this message]
2014-08-14 21:08 ` 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='CADCGFBW8CiRB7j+jsiLtjuFdku24rvnSkENwv27+aDv0tG9=jQ@mail.gmail.com' \
--to=rogerpack2005@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).