From: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
To: linux-aspeed@lists.ozlabs.org
Subject: [RFC PATCH] treewide: remove bzip2 compression support
Date: Tue, 15 Dec 2020 18:39:17 -0500 [thread overview]
Message-ID: <1608075451.ootu1tx25o.none@localhost> (raw)
In-Reply-To: <20201215190315.8681-1-alex_y_xu@yahoo.ca>
Excerpts from Alex Xu (Hello71)'s message of December 15, 2020 2:03 pm:
> 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/
>
> Signed-off-by: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
Upon further research, I found that bzip2 removal was already
implemented as part of zstd addition, but were apparently abandoned in
an effort to get zstd in. I will check those patches and try sending
those instead. Thanks to all reviewers for comments on this patch.
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: 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
Subject: Re: [RFC PATCH] treewide: remove bzip2 compression support
Date: Tue, 15 Dec 2020 18:39:17 -0500 [thread overview]
Message-ID: <1608075451.ootu1tx25o.none@localhost> (raw)
In-Reply-To: <20201215190315.8681-1-alex_y_xu@yahoo.ca>
Excerpts from Alex Xu (Hello71)'s message of December 15, 2020 2:03 pm:
> 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/
>
> Signed-off-by: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
Upon further research, I found that bzip2 removal was already
implemented as part of zstd addition, but were apparently abandoned in
an effort to get zstd in. I will check those patches and try sending
those instead. Thanks to all reviewers for comments on this patch.
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: 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
Subject: Re: [RFC PATCH] treewide: remove bzip2 compression support
Date: Tue, 15 Dec 2020 18:39:17 -0500 [thread overview]
Message-ID: <1608075451.ootu1tx25o.none@localhost> (raw)
In-Reply-To: <20201215190315.8681-1-alex_y_xu@yahoo.ca>
Excerpts from Alex Xu (Hello71)'s message of December 15, 2020 2:03 pm:
> 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/
>
> Signed-off-by: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
Upon further research, I found that bzip2 removal was already
implemented as part of zstd addition, but were apparently abandoned in
an effort to get zstd in. I will check those patches and try sending
those instead. Thanks to all reviewers for comments on this patch.
_______________________________________________
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: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [RFC PATCH] treewide: remove bzip2 compression support
Date: Tue, 15 Dec 2020 18:39:17 -0500 [thread overview]
Message-ID: <1608075451.ootu1tx25o.none@localhost> (raw)
In-Reply-To: <20201215190315.8681-1-alex_y_xu@yahoo.ca>
Excerpts from Alex Xu (Hello71)'s message of December 15, 2020 2:03 pm:
> 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/
>
> Signed-off-by: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
Upon further research, I found that bzip2 removal was already
implemented as part of zstd addition, but were apparently abandoned in
an effort to get zstd in. I will check those patches and try sending
those instead. Thanks to all reviewers for comments on this patch.
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: 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
Subject: Re: [RFC PATCH] treewide: remove bzip2 compression support
Date: Tue, 15 Dec 2020 18:39:17 -0500 [thread overview]
Message-ID: <1608075451.ootu1tx25o.none@localhost> (raw)
In-Reply-To: <20201215190315.8681-1-alex_y_xu@yahoo.ca>
Excerpts from Alex Xu (Hello71)'s message of December 15, 2020 2:03 pm:
> 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/
>
> Signed-off-by: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
Upon further research, I found that bzip2 removal was already
implemented as part of zstd addition, but were apparently abandoned in
an effort to get zstd in. I will check those patches and try sending
those instead. Thanks to all reviewers for comments on this patch.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-15 23:39 UTC|newest]
Thread overview: 25+ 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 19:03 ` Alex Xu (Hello71)
2020-12-15 19:03 ` 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 21:51 ` Michal Suchánek
2020-12-15 21:51 ` Michal Suchánek
2020-12-15 21:51 ` Michal Suchánek
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 23:39 ` Alex Xu [this message]
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
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=1608075451.ootu1tx25o.none@localhost \
--to=alex_y_xu@yahoo.ca \
--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 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.