From: Nick Piggin <piggin@cyberone.com.au>
To: Daniel Egger <degger@fhm.edu>
Cc: linux-kernel@vger.kernel.org, rob@landley.net
Subject: Re: Where's the bzip2 compressed linux-kernel patch?
Date: Sun, 19 Oct 2003 10:51:40 +1000 [thread overview]
Message-ID: <3F91E01C.4090507@cyberone.com.au> (raw)
In-Reply-To: <1066477155.5606.34.camel@sonja>
Daniel Egger wrote:
>Am Sam, den 18.10.2003 schrieb Nick Piggin um 07:30:
>
>
>>This came up on the list a while back. IIRC the conclusion was that
>>runtime memory usage and speed, and not so significant compression
>>improvement over gzip.
>>
>
>I quick test with a PowerPC kernel and the normal vmlinux image reveals
>that this is nonsense.
>
>-rwxr-xr-x 1 root root 2766490 2003-09-27 22:29 vmlinux
>-rwxr-xr-x 1 root root 1149410 2003-09-27 22:29 vmlinux.gz
>-rwxr-xr-x 1 root root 1062999 2003-09-27 22:29 vmlinux.bz2
>
>This is a 86411 bytes or 8.1% reduction, seems significant to me...
>
Sure, it might be worth it in some cases. I didn't mean improvement
wasn't measurable at all.
next prev parent reply other threads:[~2003-10-19 0:51 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 [this message]
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
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=3F91E01C.4090507@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=degger@fhm.edu \
--cc=linux-kernel@vger.kernel.org \
--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.