From: "Michal Suchánek" <msuchanek@suse.de>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-mips@vger.kernel.org,
openrisc@lists.librecores.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
linux-xtensa@linux-xtensa.org, torvalds@linux-foundation.org
Subject: Re: [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@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
WARNING: multiple messages have this Message-ID (diff)
From: "Michal Suchánek" <msuchanek@suse.de>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Cc: linux-s390@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-aspeed@lists.ozlabs.org, linux-kbuild@vger.kernel.org,
torvalds@linux-foundation.org, linux-xtensa@linux-xtensa.org,
linux-sh@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, openrisc@lists.librecores.org,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [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@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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: "Michal Suchánek" <msuchanek@suse.de>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Cc: linux-s390@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-aspeed@lists.ozlabs.org, linux-kbuild@vger.kernel.org,
torvalds@linux-foundation.org, linux-xtensa@linux-xtensa.org,
linux-sh@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, openrisc@lists.librecores.org,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [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@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
WARNING: multiple messages have this Message-ID (diff)
From: "Michal Suchánek" <msuchanek@suse.de>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Cc: linux-s390@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-aspeed@lists.ozlabs.org, linux-kbuild@vger.kernel.org,
torvalds@linux-foundation.org, linux-xtensa@linux-xtensa.org,
linux-sh@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, openrisc@lists.librecores.org,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [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@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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Michal =?unknown-8bit?q?Such=C3=A1nek?= <msuchanek@suse.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [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:52 UTC|newest]
Thread overview: 21+ 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 (Hello71)
2020-12-15 19:03 ` [OpenRISC] " Alex Xu
2020-12-15 19:03 ` Alex Xu (Hello71)
2020-12-15 19:03 ` Alex Xu (Hello71)
2020-12-15 19:03 ` Alex Xu (Hello71)
2020-12-15 21:51 ` Michal Suchánek [this message]
2020-12-15 21:51 ` [OpenRISC] " Michal =?unknown-8bit?q?Such=C3=A1nek?=
2020-12-15 21:51 ` Michal Suchánek
2020-12-15 21:51 ` Michal Suchánek
2020-12-15 21:51 ` Michal Suchánek
2020-12-15 23:39 ` Alex Xu (Hello71)
2020-12-15 23:39 ` [OpenRISC] " Alex Xu
2020-12-15 23:39 ` Alex Xu (Hello71)
2020-12-15 23:39 ` Alex Xu (Hello71)
[not found] <20201117223253.65920-1-alex_y_xu.ref@yahoo.ca>
2020-11-17 22:32 ` Alex Xu (Hello71)
2020-11-17 22:32 ` Alex Xu (Hello71)
2020-11-17 22:32 ` Alex Xu (Hello71)
2020-11-17 22:32 ` Alex Xu (Hello71)
2020-11-19 9:21 ` Rolf Eike Beer
2020-11-19 9:21 ` Rolf Eike Beer
2020-11-19 9:21 ` Rolf Eike Beer
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=alex_y_xu@yahoo.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=openrisc@lists.librecores.org \
--cc=torvalds@linux-foundation.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 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.