mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Robson <slarty2@ntlworld.com>
To: Amol Kumar Lad <amolk@ishoni.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gzip compression of vmlinux
Date: Mon, 21 Oct 2002 15:51:07 +0100	[thread overview]
Message-ID: <20021021145108.ZFJP292.mta03-svc.ntlworld.com@there> (raw)
In-Reply-To: <1035243705.2202.3.camel@amol.in.ishoni.com>

On Tuesday 22 October 2002 12:41 am, Amol Kumar Lad wrote:
> Hi,
>  Currently we use gzip to compress vmlinux ( and finally form bzImage).
> I am planning to replace it with bzip2 . Should I go ahead with it ?
> Will it find its place in the latest kernel ?
> We save some 35k of compressed bzImage using bzip2

If you replace the gzip kernel compression with bzip2, will it be easy to 
also bzip2 initrd images?

If so, does the kernel then no longer need a gzip decompression routine? Does 
the current implementation use the same gunzipper for the kernel and initrd 
(possibly not? Is the kernel gunzipper real mode?)

If so then this is a good feature for some embedded systems which can trade a 
few seconds of boot time for smaller images, particularly if it removes the 
routine from the kernel.

How much slower is bunzip2?

On my system, bunzip2 decompresses a kernel image nearly 10x slower than gzip

[mark@athlon linux-2.4.19]$ time gunzip blah
0.08user 0.01system 0:00.09elapsed 96%CPU (0avgtext+0avgdata 0maxresident)k

[mark@athlon linux-2.4.19]$ time bunzip2 blah.bz2 
0.83user 0.04system 0:00.87elapsed 99%CPU (0avgtext+0avgdata 0maxresident)k

and it only gets 6% smaller

but this is a highly unscientific test.

Mark

  parent reply	other threads:[~2002-10-21 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 23:41 Amol Kumar Lad
2002-10-21 14:43 ` Richard B. Johnson
2002-10-21 14:51 ` Mark Robson [this message]
2002-10-21 15:19 ` jbradford
2002-10-24  7:58 ` Eric W. Biederman

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=20021021145108.ZFJP292.mta03-svc.ntlworld.com@there \
    --to=slarty2@ntlworld.com \
    --cc=amolk@ishoni.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®