All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Efremov <efremov@linux.com>
To: sedat.dilek@gmail.com
Cc: linux-kbuild@vger.kernel.org, Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH] kbuild: add variables for compression tools
Date: Thu, 4 Jun 2020 16:55:03 +0300	[thread overview]
Message-ID: <635d02d6-05a9-7620-c386-dac766cd49da@linux.com> (raw)
In-Reply-To: <CA+icZUU7AAzpYfktqCvn8oKpFMzZud6fQEh=fNWi4xkuqKmYog@mail.gmail.com>

Hi,

On 6/4/20 4:05 PM, Sedat Dilek wrote:
> Hi Denis,
> 
> is it possible to add ZSTD compression support with the possibility to
> add - for example multithreading - options?

Where do you want to use zstd in kernel?

For example, to compress headers xz is used, to compress /proc/config.gz
gzip is used. It could be relatively easy patched to use zstd for it and
it could be easy to add tarzstd-pkg target for building the kernel
as a zstd compressed tarball. However, I doubt that someone really needs it.
xz is best for headers because of compression ratio, gzip is best for config
because gzip is installed by default on most systems.
To compress modules, ramdisk or kernel image with zstd one needs
to implement zstd decompression algorithm in kernel. Given that there
are already gzip,bzip2,lzma,xz,lzo,lz4 I really doubt that it will be
useful. There should be a good comparison showing that kernel image
with zstd, for example, beats gzip and couple of others in comression ratio
and decompression speed to properly position the zstd algo.

> For the documentation - which I have not checked - are the tools and
> libs mentioned you will need to have installed for certain compression
> tools?

gzip, bzip2 are already installed on most systems. It's highly likely that
lzo, lzma, xz will require you to install them.

Thanks,
Denis

  reply	other threads:[~2020-06-04 13:55 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 [this message]
2020-06-04 16:07   ` Sedat Dilek
2020-06-04 17:01     ` Denis Efremov
2020-06-04 17:05       ` Sedat Dilek
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=635d02d6-05a9-7620-c386-dac766cd49da@linux.com \
    --to=efremov@linux.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=sedat.dilek@gmail.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.