All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Leber <christian@leber.de>
To: linux-kernel@vger.kernel.org
Cc: mpm@selenic.com
Subject: Re: Easy trick to reduce kernel footprint
Date: Mon, 6 Jun 2005 03:10:56 +0200	[thread overview]
Message-ID: <20050606011056.GB18603@core.home> (raw)
In-Reply-To: <20050605223528.GA13726@alpha.home.local>

On Mon, Jun 06, 2005 at 12:35:28AM +0200, Willy Tarreau wrote:

> saves 23 kB (2%) on the overall image without touching any code. The LZMA
> implementation could save 145 kB (12%), but would require a different
> extraction code (I've already seen patches to bring LZMA support on 2.4).

The patch for 2.4 is here:
http://www.zelow.no/floppyfw/download/Development/Patches/kernel/040-lzma-vmlinuz.diff
and it actually works.

My not working patch is here:
http://debian.christian-leber.de/kernel_lzma/lzma_image.patch
you have to apply the patch from the other mail before.
(or here: http://debian.christian-leber.de/kernel_lzma/lzma_ramdisk.patch)

If you just want to see how it doesn't work, here is a kernel image to
see it failing in qemu, basically it just decompresses again and again.
http://debian.christian-leber.de/kernel_lzma/bzImage

The decompression works correctly(checksum), i think the problem is the address
where the decompressed kernel image should be, i just can't get out how
this piece of code is supposed to work.

Therefore it could be a small problem only.


Another minor problem of lzma is that you need slightly more memory than
with gzip. (at least when you can't have the output in a continuous
piece of memory)
On the plus side is also that the lzma decompression code itself is
smaller and doesn't have such a ugly "interface".


Christian Leber

-- 
http://www.nosoftwarepatents.com


  parent reply	other threads:[~2005-06-06  1:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05 22:35 Easy trick to reduce kernel footprint Willy Tarreau
2005-06-05 23:41 ` Christian Leber
2005-06-06  1:02 ` Wakko Warner
2005-06-06  4:11   ` Willy Tarreau
2005-06-06 11:07     ` Wakko Warner
2005-06-06 11:43       ` Willy Tarreau
2005-06-06 20:16         ` Wakko Warner
2005-06-06  1:10 ` Christian Leber [this message]
2005-06-06  7:47 ` Jörn Engel
2005-06-06  5:55   ` Oliver Leitner
2005-06-06  8:19   ` Willy Tarreau
2005-06-06  9:46     ` Jörn Engel
2005-06-06  8:31   ` Christian Leber

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=20050606011056.GB18603@core.home \
    --to=christian@leber.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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.