From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Nick Terrell <terrelln@fb.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
kernel-team@fb.com, Chris Mason <clm@fb.com>,
Yann Collet <cyan@fb.com>, David Sterba <dsterba@suse.cz>,
squashfs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Add xxhash and zstd modules
Date: Mon, 24 Jul 2017 09:44:35 -0400 [thread overview]
Message-ID: <b1019eff-f91b-a7e6-288a-b93d1ac54b30@gmail.com> (raw)
In-Reply-To: <20170722113503.nf227bdrzx6637wl@angband.pl>
On 2017-07-22 07:35, Adam Borowski wrote:
> On Fri, Jul 21, 2017 at 11:56:21AM -0400, Austin S. Hemmelgarn wrote:
>> On 2017-07-20 17:27, Nick Terrell wrote:
>>> This patch set adds xxhash, zstd compression, and zstd decompression
>>> modules. It also adds zstd support to BtrFS and SquashFS.
>>>
>>> Each patch has relevant summaries, benchmarks, and tests.
>>
>> For patches 2-3, I've compile tested and had runtime testing running for
>> about 18 hours now with no issues, so you can add:
>>
>> Tested-by: Austin S. Hemmelgarn <ahferroin7@gmail.com>
>
> I assume you haven't tried it on arm64, right?
>
> I had no time to get 'round to it before, and just got the following build
> failure:
>
> CC fs/btrfs/zstd.o
> In file included from fs/btrfs/zstd.c:28:0:
> fs/btrfs/compression.h:39:2: error: unknown type name ‘refcount_t’
> refcount_t pending_bios;
> ^~~~~~~~~~
> scripts/Makefile.build:302: recipe for target 'fs/btrfs/zstd.o' failed
>
> It's trivially fixably by:
> --- a/fs/btrfs/zstd.c
> +++ b/fs/btrfs/zstd.c
> @@ -24,6 +24,7 @@
> #include <linux/sched.h>
> #include <linux/pagemap.h>
> #include <linux/bio.h>
> +#include <linux/refcount.h>
> #include <linux/zstd.h>
> #include "compression.h"
>
> after which it works fine, although half an hour of testing isn't exactly
> exhaustive.
I did, and didn't hit this somehow...
Off to go verify my tool-chain and scripts then...
>
>
> Alas, the armhf machine I ran stress tests (Debian archive rebuilds) on
> doesn't boot with 4.13-rc1 due to some unrelated regression, bisecting that
> would be quite painful so I did not try yet. I guess re-testing your patch
> set on 4.12, even with btrfs-for-4.13 (which it had for a while), wouldn't
> be of much help. So far, previous versions have been running for weeks,
> with no issue since you fixed workspace flickering.
I also didn't see this, but I test on some seriously bare-bones
configurations for both the 32-bit ARM tests I run. On further
inspection, it looks like my scripts decided to use btrfs-for-4.13 as
the base, not 4.13-rc1 like I thought they did, so I don't know anymore
how helpful my testing may have been.
>
>
> On amd64 all is fine.
>
>
> I haven't tested SquashFS at all.
>
>
> Meow!
>
prev parent reply other threads:[~2017-07-24 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 21:27 [PATCH v3 0/4] Add xxhash and zstd modules Nick Terrell
2017-07-20 21:27 ` [PATCH v3 1/4] lib: Add xxhash module Nick Terrell
2017-07-20 21:27 ` [PATCH v3 3/4] btrfs: Add zstd support Nick Terrell
2017-07-23 19:28 ` kbuild test robot
2017-07-24 17:25 ` kbuild test robot
2017-07-25 23:19 ` Giovanni Cabiddu
2017-08-18 15:37 ` David Sterba
2017-07-20 21:27 ` [PATCH v3 4/4] squashfs: " Nick Terrell
2017-07-31 1:50 ` Phillip Lougher
2017-07-31 2:18 ` Phillip Lougher
2017-07-31 21:30 ` Nick Terrell
2017-07-21 11:16 ` [PATCH v3 0/4] Add xxhash and zstd modules Austin S. Hemmelgarn
2017-07-21 11:18 ` Austin S. Hemmelgarn
2017-07-21 15:56 ` Austin S. Hemmelgarn
2017-07-22 11:35 ` Adam Borowski
2017-07-24 13:44 ` Austin S. Hemmelgarn [this message]
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=b1019eff-f91b-a7e6-288a-b93d1ac54b30@gmail.com \
--to=ahferroin7@gmail.com \
--cc=clm@fb.com \
--cc=cyan@fb.com \
--cc=dsterba@suse.cz \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-team@fb.com \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@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).