From: Nick Terrell <terrelln@fb.com>
To: David Sterba <dsterba@suse.cz>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
"Eric Biggers" <ebiggers@kernel.org>,
"Nick Terrell" <nickrterrell@gmail.com>,
"squashfs-devel@lists.sourceforge.net"
<squashfs-devel@lists.sourceforge.net>,
"Christoph Hellwig" <hch@infradead.org>,
"Yann Collet" <cyan@fb.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
"Petr Malat" <oss@malat.biz>, "Chris Mason" <clm@fb.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"Kernel Team" <Kernel-team@fb.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Niket Agarwal" <niketa@fb.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
"Johannes Weiner" <jweiner@fb.com>
Subject: Re: [f2fs-dev] [PATCH v7 0/3] Update to zstd-1.4.6
Date: Wed, 16 Dec 2020 22:07:38 +0000 [thread overview]
Message-ID: <6C449BCE-E7DB-4EE6-B4F5-FED3977BD8F0@fb.com> (raw)
In-Reply-To: <20201216185052.GL6430@twin.jikos.cz>
> On Dec 16, 2020, at 10:50 AM, David Sterba <dsterba@suse.cz> wrote:
>
> On Wed, Dec 16, 2020 at 11:58:07AM +1100, Herbert Xu wrote:
>> On Wed, Dec 16, 2020 at 12:48:51AM +0000, Nick Terrell wrote:
>>>
>>> Thanks for the advice! The first zstd patches went through Herbert’s tree, which is
>>> why I’ve sent them this way.
>>
>> Sorry, but I'm not touch these patches as Christoph's objections
>> don't seem to have been addressed.
>
> I have objections to the current patchset as well, the build bot has
> found that some of the function frames are overly large (up to 3800
> bytes) [1],
Sorry I missed your reply David, it didn’t make it to my inbox.
Compiled with x86-64, arm, and aarch64 that function does not trigger any
-Wframe-larger-than= warnings during the kernel build. It seems like the
compiler backend for the parisc architecture (the architecture that the build
bot used) is doing a particularly bad job at optimizing this function, because
there is nothing in there that should be using that much stack space.
I have a test in upstream zstd that measures the stack high water mark for
all usage of zstd compression currently in-use the kernel. It says that zstd
uses 2KB of stack space in total on x86-64. I used this test to remove 1KB of
stack usage from upstream zstd. But, this is still 400 bytes more than the
current version of zstd in the kernel. I will look into squeezing out those last
400 bytes of stack usage.
> besides the original complaint that the patch 3/3 is 1.5MiB.
>
> [1] https://lore.kernel.org/lkml/20201204140314.GS6430@twin.jikos.cz/
It is very large. If it helps, in the commit message I’ve provided this link [0],
which provides the diff between upstream zstd as-is and the imported zstd,
which has been modified by the automated tooling to work in the kernel.
[0] https://github.com/terrelln/linux/commit/ac2ee65dcb7318afe426ad08f6a844faf3aebb41
Best,
Nick
next prev parent reply other threads:[~2020-12-16 22:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 20:51 [PATCH v7 0/3] Update to zstd-1.4.6 Nick Terrell
2020-12-03 20:51 ` [PATCH v7 1/3] lib: zstd: Add kernel-specific API Nick Terrell
2020-12-03 20:51 ` [PATCH v7 2/3] lib: zstd: Add decompress_sources.h for decompress_unzstd Nick Terrell
2020-12-03 20:51 ` [PATCH v7 3/3] lib: zstd: Upgrade to latest upstream zstd version 1.4.6 Nick Terrell
2020-12-15 20:58 ` [PATCH v7 0/3] Update to zstd-1.4.6 Nick Terrell
2020-12-16 0:00 ` [f2fs-dev] " Eric Biggers
2020-12-16 0:48 ` Nick Terrell
2020-12-16 0:58 ` Herbert Xu
2020-12-16 1:12 ` Nick Terrell
2020-12-16 18:50 ` David Sterba
2020-12-16 22:07 ` Nick Terrell [this message]
2020-12-17 1:23 ` Michał Mirosław
2020-12-18 18:57 ` Nick Terrell
2021-02-27 9:33 ` Oleksandr Natalenko
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=6C449BCE-E7DB-4EE6-B4F5-FED3977BD8F0@fb.com \
--to=terrelln@fb.com \
--cc=Kernel-team@fb.com \
--cc=clm@fb.com \
--cc=cyan@fb.com \
--cc=dsterba@suse.cz \
--cc=ebiggers@kernel.org \
--cc=hch@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=jweiner@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=nickrterrell@gmail.com \
--cc=niketa@fb.com \
--cc=oss@malat.biz \
--cc=squashfs-devel@lists.sourceforge.net \
/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).