From: Michal Suchánek <msuchanek@suse.de>
To: linux-aspeed@lists.ozlabs.org
Subject: [RFC PATCH] treewide: remove bzip2 compression support
Date: Tue, 15 Dec 2020 22:51:57 +0100 [thread overview]
Message-ID: <20201215215157.GJ6564@kitsune.suse.cz> (raw)
In-Reply-To: <20201215190315.8681-1-alex_y_xu@yahoo.ca>
Hello,
On Tue, Dec 15, 2020 at 02:03:15PM -0500, Alex Xu (Hello71) wrote:
> bzip2 is either slower or larger than every other supported algorithm,
> according to benchmarks at [0]. It is far slower to decompress than any
> other algorithm, and still larger than lzma, xz, and zstd.
>
> [0] https://lore.kernel.org/lkml/1588791882.08g1378g67.none at localhost/
Sounds cool. I wonder how many people will complain that their
distribution migrated to bzip2 but got stuck there and now new kernels
won't work on there with some odd tool or another :p
> @@ -212,11 +209,6 @@ choice
> Compression speed is only relevant when building a kernel.
> Decompression speed is relevant at each boot.
>
> - If you have any problems with bzip2 or lzma compressed
> - kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older
> - version of this functionality (bzip2 only), for 2.4, was
> - supplied by Christian Ludwig)
> -
Shouldn't the LZMA part be preserved here?
Thanks
Michal
next prev parent reply other threads:[~2020-12-15 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201215190315.8681-1-alex_y_xu.ref@yahoo.ca>
2020-12-15 19:03 ` [RFC PATCH] treewide: remove bzip2 compression support Alex Xu
2020-12-15 21:51 ` Michal Suchánek [this message]
2020-12-15 23:39 ` Alex Xu
[not found] <20201117223253.65920-1-alex_y_xu.ref@yahoo.ca>
2020-11-17 22:32 ` Alex Xu
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=20201215215157.GJ6564@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=linux-aspeed@lists.ozlabs.org \
/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).