From: Willy Tarreau <willy@w.ods.org>
To: Rob Landley <rob@landley.net>
Cc: Willy Tarreau <willy@w.ods.org>,
Michael Buesch <mbuesch@freenet.de>,
Nick Piggin <piggin@cyberone.com.au>,
Daniel Egger <degger@fhm.edu>,
linux-kernel@vger.kernel.org
Subject: Re: Where's the bzip2 compressed linux-kernel patch?
Date: Mon, 20 Oct 2003 06:28:37 +0200 [thread overview]
Message-ID: <20031020042837.GA4994@alpha.home.local> (raw)
In-Reply-To: <200310191900.47300.rob@landley.net>
On Sun, Oct 19, 2003 at 07:00:47PM -0500, Rob Landley wrote:
> upx is upx-1.22.
>
> So you're talking about something that compresses LESS well than gzip. Why?
I'm not talking about something that compresses LESS than gzip, I'm talking
about something I almost always use to recompress my kernels and reduce their
size by 20% over gzip, and decompress way faster.
It's upx-1.90 (which is able to decompress/recompress bzimage). OK it's still
a development version, but it has already saved me megs of flash.
I don't know how the tests above were done. But what I know for sure is that
there are excessive open source zealots who would only download the OSS
version of UPX which uses the UCL library while the closed source version
uses the NRV one which is a jewel.
And you know what ? when I put a complete distro on a 8MB flash, my primary
concern is to save as much space as possible, and my ability to read the
compressor sources only comes next.
BTW, I don't remember every upx argument, but I'm sure I got best numbers
with '--best --crp-ms=100000'.
> And no, gzip -9 does not add anything to decompression time, only
> compression time.
Where did you get this interesting idea ? every decompressor needs
decompression time. You need the compressed kernel to be in memory, then you
decompress it, then you boot it. On my old 386sx which was still my home
firewall 6 months ago, the kernel would take 2-3 seconds to decompress with
gzip while it was almost unnoticeable with upx (which did it in place, BTW).
Now don't get me wrong, I'm not advertising for upx. But bzip2 was proposed
and will always be criticized because of its decompression time and cost in
terms of memory. So I simply suggested to take a look at other solutions
which seem interesting. An UPX-based implementation seems interesting to me
only if the decompression code is free and can be put in the kernel. Otherwise
it is not. If the numbers above come from the UCL lib, then we at least know
that this one doesn't interest us for this matter. Some people would also
suggest taking a look at other compression algorithms which can be of
interest, but I don't know their sources status (open/close).
> I can make bunzip work in-place if you'd like
That's very important for low-memory systems.
Regards,
Willy
next prev parent reply other threads:[~2003-10-20 4:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 5:18 Where's the bzip2 compressed linux-kernel patch? Rob Landley
2003-10-18 5:30 ` Nick Piggin
2003-10-18 11:39 ` Daniel Egger
2003-10-19 0:51 ` Nick Piggin
2003-10-19 10:45 ` Michael Buesch
2003-10-19 21:04 ` Willy Tarreau
2003-10-19 21:27 ` Michael Buesch
2003-10-20 0:00 ` Rob Landley
2003-10-20 4:28 ` Willy Tarreau [this message]
2003-10-20 4:52 ` Valdis.Kletnieks
2003-10-20 5:47 ` Rob Landley
2003-10-20 11:55 ` Willy Tarreau
2003-10-19 22:15 ` Rob Landley
2003-10-18 6:05 ` Erik Andersen
2003-10-18 16:43 ` Jörn Engel
2003-10-18 20:38 ` Rob Landley
2003-10-20 8:31 ` Jörn Engel
2003-10-20 9:41 ` Rob Landley
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=20031020042837.GA4994@alpha.home.local \
--to=willy@w.ods.org \
--cc=degger@fhm.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.de \
--cc=piggin@cyberone.com.au \
--cc=rob@landley.net \
/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.