From: "René Rebe" <rene@exactcode.com>
To: Nick Terrell <terrelln@fb.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: zstd kernel and initrd compression
Date: Thu, 5 Oct 2017 10:17:31 +0200 [thread overview]
Message-ID: <76B54446-B110-4CF0-BCA0-3AB94B44AFD3@exactcode.com> (raw)
In-Reply-To: <0A00541D-A411-4BE7-BBA8-8459BC62BDE1@fb.com>
Hi Nick,
On Oct 5, 2017, at 1:29, Nick Terrell <terrelln@fb.com> wrote:
> On 10/4/17, 3:01 AM, "linux-kernel-owner@vger.kernel.org on behalf of René Rebe" <linux-kernel-owner@vger.kernel.org on behalf of rene@exactcode.com> wrote:
>> Hi,
>>
>> I noticed zstd compression was recently added for btrfs and squashfs.
>> Are there actually already patches floating around for zstd kernel and intird compression?
>> Looks like that would be a quite nice fit regarding speed and compression ratio, …
>>
>> Regards,
>> René
>
> I started working on some patches yesterday, and just got zstd kernel,
> initrd, and initramfs compression working today. I think I'll be ready to
> send the patches out within a week.
awesome, if you have something to test I could give it a try on my test bench, too.
Regards,
René
--
ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
http://exactcode.com | http://exactscan.com | http://ocrkit.com | http://t2-project.org | http://rene.rebe.de
next prev parent reply other threads:[~2017-10-05 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 10:00 zstd kernel and initrd compression René Rebe
2017-10-04 23:29 ` Nick Terrell
2017-10-05 8:17 ` René Rebe [this message]
2017-10-05 19:22 ` [PREVIEW] Add x86 zstd kernel compression Nick Terrell
2017-10-05 21:15 ` René Rebe
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=76B54446-B110-4CF0-BCA0-3AB94B44AFD3@exactcode.com \
--to=rene@exactcode.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.