From: Chris Mason <clm@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Nick Terrell <terrelln@fb.com>,
Phillip Lougher <phillip@squashfs.org.uk>,
Sean Purcell <me@seanp.xyz>
Cc: David Sterba <dsterba@suse.cz>
Subject: Re: [GIT PULL] zstd support (lib, btrfs, squashfs)
Date: Fri, 8 Sep 2017 20:43:52 -0400 [thread overview]
Message-ID: <c721b754-aee4-d1ac-3fa7-64fd6c7725c1@fb.com> (raw)
In-Reply-To: <de155140-8773-1a78-2dab-1d722ede3dc1@fb.com>
On 09/08/2017 03:33 PM, Chris Mason wrote:
> Hi Linus,
>
> Nick Terrell's patch series to add zstd support to the kernel has been
> floating around for a while. After talking with Dave Sterba, Herbert and
> Phillip, we decided to send the whole thing in as one pull request.
>
> I have it in my zstd branch:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git zstd
>
> There's a trivial conflict with the main btrfs pull that Dave Sterba just
> sent. His pull deletes BTRFS_COMPRESS_LAST in fs/btrfs/compression.h, and
> I've put the sample resolution in a branch named zstd-4.14-merge. My
> idea was that you'd take our main btrfs pull first and this one second,
> but the conflicts are small enough it's not a big deal.
>
> zstd is a big win in speed over zlib and in compression ratio over lzo, and
> the compression team here at FB has gotten great results using it in production.
> Nick will continue to update the kernel side with new improvements from the
> open source zstd userland code.
Just to clarify, we've been testing the kernel side of this here at FB,
but our zstd use in prod is limited to the application side.
-chris
next prev parent reply other threads:[~2017-09-09 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 19:33 [GIT PULL] zstd support (lib, btrfs, squashfs) Chris Mason
2017-09-09 0:43 ` Chris Mason [this message]
2017-09-09 1:35 ` Herbert Xu
2017-09-09 2:19 ` Chris Mason
2017-09-09 2:48 ` Nick Terrell
2017-09-09 4:14 ` Herbert Xu
2017-09-11 19:24 ` [GIT PULL v2] zstd support (lib, btrfs, squashfs, nocrypto) Chris Mason
2017-09-12 6:30 ` Phillip Lougher
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=c721b754-aee4-d1ac-3fa7-64fd6c7725c1@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=herbert@gondor.apana.org.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@seanp.xyz \
--cc=phillip@squashfs.org.uk \
--cc=terrelln@fb.com \
--cc=torvalds@linux-foundation.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).