From: David Woodhouse <dwmw2@infradead.org>
To: Rui Salvaterra <rsalvaterra@gmail.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: lizhe67@huawei.com, christian.brauner@ubuntu.com,
gustavoars@kernel.org, trix@redhat.com, keescook@chromium.org
Subject: Re: [RFC PATCH v2] jffs2: add support for zstd compression
Date: Mon, 26 Apr 2021 09:24:03 +0100 [thread overview]
Message-ID: <ee050b2dce3a233318748df416be0ebff4402ed2.camel@infradead.org> (raw)
In-Reply-To: <CALjTZvaX8miSycr4oGmF_rGN4KWWBzfyBj1-7jefT=Uz3w9Oww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
On Thu, 2021-03-25 at 14:47 +0000, Rui Salvaterra wrote:
> Friendly ping (and also cc'ing dwmw2).
>
> On Tue, 16 Mar 2021 at 14:19, Rui Salvaterra <rsalvaterra@gmail.com> wrote:
> >
> > Implement support for zstd compression in jffs2 at the default compression
> > level (3).
> >
> > Lightly tested in OpenWrt, on a single CPU embedded MIPS32 system (AirGrid M2).
Seems reasonable. Do you have the corresponding addition for mkfs.jffs2
and can you report the boot time / image sizes with it vs. zlib on a
typical platform?
And if it doesn't make a difference to boot time or image size... why
are we doing it?
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2021-04-26 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 14:19 Rui Salvaterra
2021-03-25 14:47 ` Rui Salvaterra
2021-04-26 7:45 ` Rui Salvaterra
2021-04-26 8:24 ` David Woodhouse [this message]
2021-04-26 8:49 ` Rui Salvaterra
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=ee050b2dce3a233318748df416be0ebff4402ed2.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=christian.brauner@ubuntu.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lizhe67@huawei.com \
--cc=rsalvaterra@gmail.com \
--cc=trix@redhat.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
all inboxes | Powered by JetHome®