From: Neal Gompa <ngompa13@gmail.com>
To: Amy Parker <enbyamy@gmail.com>
Cc: Jim N <northrup.james@gmail.com>,
dsterba@suse.cz, Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Adding LZ4 compression support to Btrfs
Date: Thu, 25 Feb 2021 19:21:06 -0500 [thread overview]
Message-ID: <CAEg-Je-QP+6ad649L-vQDctfQbsHm_d4-NpGOwCKATHM0LamTA@mail.gmail.com> (raw)
In-Reply-To: <CAE1WUT7JOyeWi8DHZS3fNMAq+GX9qsm7iPC01x60m1W84ZdPrA@mail.gmail.com>
On Thu, Feb 25, 2021 at 6:18 PM Amy Parker <enbyamy@gmail.com> wrote:
>
> Thanks for your comments, Jim. I was originally going to abandon my
> thoughts about LZ4 on btrfs - but I didn't realize that FAQ was from
> 2014.
>
> > lz4 has had ongoing development and now exists in other linux kernel fs's.
> What other filesystems currently employ LZ4? Not as familiar with it
> being used on other filesystems.
>
In the Linux kernel, both SquashFS and F2FS have LZ4 compression support.
--
真実はいつも一つ!/ Always, there's only one truth!
next prev parent reply other threads:[~2021-02-26 0:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 22:50 Adding LZ4 compression support to Btrfs Amy Parker
2021-02-25 13:18 ` Neal Gompa
2021-02-25 13:26 ` David Sterba
2021-02-25 18:50 ` Eric Biggers
2021-02-26 3:54 ` Gao Xiang
2021-02-26 9:36 ` David Sterba
2021-02-26 11:28 ` Gao Xiang
2021-02-26 13:11 ` Gao Xiang
2021-02-26 14:12 ` David Sterba
2021-02-26 14:35 ` Gao Xiang
2021-02-26 16:39 ` Eric Biggers
2021-03-05 13:55 ` David Sterba
[not found] ` <CAPkEcwjcRgnaWLmqM1jEvH5A9PijsQEY5BKFyKdt_+TeugaJ_g@mail.gmail.com>
2021-02-25 23:18 ` Amy Parker
2021-02-26 0:21 ` Neal Gompa [this message]
2021-02-25 13:32 ` Filipe Manana
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=CAEg-Je-QP+6ad649L-vQDctfQbsHm_d4-NpGOwCKATHM0LamTA@mail.gmail.com \
--to=ngompa13@gmail.com \
--cc=dsterba@suse.cz \
--cc=enbyamy@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=northrup.james@gmail.com \
/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).