All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org, mpm@selenic.com
Subject: Re: Easy trick to reduce kernel footprint
Date: Mon, 6 Jun 2005 16:16:14 -0400	[thread overview]
Message-ID: <20050606201613.GA23919@animx.eu.org> (raw)
In-Reply-To: <20050606114342.GA15757@alpha.home.local>

Willy Tarreau wrote:
> On Mon, Jun 06, 2005 at 07:07:43AM -0400, Wakko Warner wrote:
>  
> > My initramfs is passed via initrd so that I can change any aspect of it with
> > out recompiling the kernel (or maybe i could use a better understanding of
> > initramfs)  I compared bzImage to bupxImage and the savings I got was around
> > 50kb difference IIRC.
> 
> With what algo and what kernel size ?
> With the close-source upx-1.93 linked with the NRV compression, I often
> observe an average 15-20% gain on the bzImage size if it does not embed
> an initramfs. I remember that the UCL library was not as good as the NRV,
> so I've stopped using it a long time ago.

I'm using upx-ucl-beta v1.91+0.20030910cvs-2 debian package.
Command line:
upx-ucl-beta -9 -f bupxImage-2.6.12-rc6
-rw-r--r--  3 root root 618442 Jun  6 16:14 bupxImage-2.6.12-rc6
-rwxrwxrwx  1 root root 669106 Jun  6 16:14 bzImage-2.6.12-rc6*
50664 bytes savings.
the kernel I have there is 100% modular except that ramdisk is compiled in. 
It was also compiled with -Os (Optimize for size config option) using gcc
3.3.5.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

  reply	other threads:[~2005-06-06 20:24 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 [this message]
2005-06-06  1:10 ` Christian Leber
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=20050606201613.GA23919@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=willy@w.ods.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.