From: Sedat Dilek <sedat.dilek@gmail.com>
To: efremov@linux.com
Cc: linux-kbuild@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Nick Terrell <terrelln@fb.com>
Subject: Re: [PATCH] kbuild: add variables for compression tools
Date: Thu, 4 Jun 2020 19:05:16 +0200 [thread overview]
Message-ID: <CA+icZUVfXwVfouPpFeBR5=TxOAT6XWDnpjhPmxTMpajV8Rs-gw@mail.gmail.com> (raw)
In-Reply-To: <a9615332-f735-4c7a-0368-f3a0402f611b@linux.com>
On Thu, Jun 4, 2020 at 7:01 PM Denis Efremov <efremov@linux.com> wrote:
>
> >
> > me and other people use "support for ZSTD-compressed kernel and
> > initramfs" for a long time successfully.
> >
> > I have modified Debian's initramfs-tools package to support creating
> > such an initrd.img and boot it successfully.
> > See Debian Bug #955469.
> >
> > There is a pull-request sent out to integrate into Linus tree.
> >
> > Some numbers from Nick Terell in his pull-request:
> > "
> > The zstd compressed kernel is smaller than the gzip compressed kernel but larger
> > than the xz or lzma compressed kernels, and it decompresses faster than
> > everything except lz4. See the table below for the measurement of an x86_64
> > kernel ordered by compressed size:
> >
> > algo size
> > xz 6,509,792
> > lzma 6,856,576
> > zstd 7,399,157
> > gzip 8,522,527
> > bzip 8,629,603
> > lzo 9,808,035
> > lz4 10,705,570
> > none 32,565,672
> > "
> >
> > More numbers in [0].
> >
> > Hope this helps you to position the zstd algo.
>
> Well, I didn't know that it's already implemented.
>
> My patch simply adds variables like GZIP, BZIP2, etc to the top makefile.
> Unfortunately there is no ZSTD in kernel now. Maybe it's in the linux-next?
> I can't see it. If my patch will be accepted to the mainline then it will
> be reasonable to add ZSTD var in makefiles as soon as zstd compression
> will be merged.
>
No, it was not merged anywhere AFAICS.
If you want to test please pull from [1].
I am using it on top of Linux v5.7.
- Sedat -
[1] https://github.com/terrelln/linux/commits/zstd-v5
next prev parent reply other threads:[~2020-06-04 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 13:05 [PATCH] kbuild: add variables for compression tools Sedat Dilek
2020-06-04 13:55 ` Denis Efremov
2020-06-04 16:07 ` Sedat Dilek
2020-06-04 17:01 ` Denis Efremov
2020-06-04 17:05 ` Sedat Dilek [this message]
2020-06-04 17:18 ` Sedat Dilek
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='CA+icZUVfXwVfouPpFeBR5=TxOAT6XWDnpjhPmxTMpajV8Rs-gw@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=efremov@linux.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@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.