From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>, Chris Mason <clm@fb.com>,
Eric Biggers <ebiggers3@gmail.com>,
Nick Terrell <terrelln@fb.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
kernel-team@fb.com, squashfs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v5 2/5] lib: Add zstd modules
Date: Thu, 10 Aug 2017 15:54:59 -0400 [thread overview]
Message-ID: <aaaede17-3493-d527-5d9b-cd105865ca24@gmail.com> (raw)
In-Reply-To: <20170810192506.GF7140@carfax.org.uk>
On 2017-08-10 15:25, Hugo Mills wrote:
> On Thu, Aug 10, 2017 at 01:41:21PM -0400, Chris Mason wrote:
>> On 08/10/2017 04:30 AM, Eric Biggers wrote:
>>>
>>> Theses benchmarks are misleading because they compress the whole file as a
>>> single stream without resetting the dictionary, which isn't how data will
>>> typically be compressed in kernel mode. With filesystem compression the data
>>> has to be divided into small chunks that can each be decompressed independently.
>>> That eliminates one of the primary advantages of Zstandard (support for large
>>> dictionary sizes).
>>
>> I did btrfs benchmarks of kernel trees and other normal data sets as
>> well. The numbers were in line with what Nick is posting here.
>> zstd is a big win over both lzo and zlib from a btrfs point of view.
>>
>> It's true Nick's patches only support a single compression level in
>> btrfs, but that's because btrfs doesn't have a way to pass in the
>> compression ratio. It could easily be a mount option, it was just
>> outside the scope of Nick's initial work.
>
> Could we please not add more mount options? I get that they're easy
> to implement, but it's a very blunt instrument. What we tend to see
> (with both nodatacow and compress) is people using the mount options,
> then asking for exceptions, discovering that they can't do that, and
> then falling back to doing it with attributes or btrfs properties.
> Could we just start with btrfs properties this time round, and cut out
> the mount option part of this cycle.
AFAIUI, the intent is to extend the compression type specification for
both the mount options and the property, not to add a new mount option.
I think we all agree that `mount -o compress=zstd3` is a lot better than
`mount -o compress=zstd,compresslevel=3`.
>
> In the long run, it'd be great to see most of the btrfs-specific
> mount options get deprecated and ultimately removed entirely, in
> favour of attributes/properties, where feasible.
Are properties set on the root subvolume inherited properly? Because
unless they are, we can't get the same semantics.
Two other counter arguments on completely removing BTRFS-specific mount
options:
1. It's a lot easier and a lot more clearly defined to change things
that affect global behavior of the FS by a remount than having to
iterate everything in the FS to update properties. If I'm disabling
autodefrag, I'd much rather just `mount -o remount,noautodefrag` than
`find / -xdev -exec btrfs property set \{\} autodefrag false`, as the
first will take effect for everything simultaneously and run
exponentially quicker.
2. There are some things that don't make sense as per-object settings or
are otherwise nonsensical on objects. Many, but not all, of the BTRFS
specific mount options fall into this category IMO, with the notable
exception of compress[-force], [no]autodefrag, [no]datacow, and
[no]datasum. Some other options do make sense as properties of the
filesystem (commit, flushoncommit, {inode,space}_cache, max_inline,
metadata_ratio, [no]ssd, and [no]treelog are such options), but many are
one-off options that affect behavior on mount (like skip_balance,
clear_cache, nologreplay, norecovery, usebbackuproot, and subvol).
next prev parent reply other threads:[~2017-08-10 19:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 2:35 [PATCH v5 0/5] Add xxhash and zstd modules Nick Terrell
2017-08-10 2:35 ` [PATCH v5 1/5] lib: Add xxhash module Nick Terrell
2017-08-10 2:35 ` [PATCH v5 2/5] lib: Add zstd modules Nick Terrell
2017-08-10 8:30 ` Eric Biggers
2017-08-10 11:32 ` Austin S. Hemmelgarn
2017-08-10 14:57 ` Austin S. Hemmelgarn
2017-08-10 17:36 ` Eric Biggers
2017-08-10 17:24 ` Eric Biggers
2017-08-10 17:47 ` Austin S. Hemmelgarn
2017-08-10 19:24 ` Nick Terrell
2017-08-10 17:41 ` Chris Mason
2017-08-10 19:00 ` Eric Biggers
2017-08-10 19:07 ` Chris Mason
2017-08-10 19:25 ` Hugo Mills
2017-08-10 19:54 ` Austin S. Hemmelgarn [this message]
2017-08-11 13:20 ` Chris Mason
2017-08-14 13:30 ` David Sterba
2017-08-10 19:16 ` Nick Terrell
2017-08-10 2:39 ` [PATCH v5 3/5] btrfs: Add zstd support Nick Terrell
2017-08-11 2:13 ` Adam Borowski
2017-08-11 3:23 ` Nick Terrell
2017-08-11 11:45 ` Austin S. Hemmelgarn
2017-08-10 2:42 ` [PATCH v5 4/5] squashfs: " Nick Terrell
2017-08-10 2:43 ` [PATCH v5 5/5] crypto: " Nick Terrell
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=aaaede17-3493-d527-5d9b-cd105865ca24@gmail.com \
--to=ahferroin7@gmail.com \
--cc=clm@fb.com \
--cc=ebiggers3@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=hugo@carfax.org.uk \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=squashfs-devel@lists.sourceforge.net \
--cc=terrelln@fb.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).