From: Willy Tarreau <willy@w.ods.org>
To: linux-kernel@vger.kernel.org, mpm@selenic.com
Subject: Re: Easy trick to reduce kernel footprint
Date: Mon, 6 Jun 2005 06:11:01 +0200 [thread overview]
Message-ID: <20050606041101.GA14799@alpha.home.local> (raw)
In-Reply-To: <20050606010246.GA22252@animx.eu.org>
On Sun, Jun 05, 2005 at 09:02:46PM -0400, Wakko Warner wrote:
> Willy Tarreau wrote:
> > Here's a simple trick for all those who try to squeeze their kernels to the
> > absolute smallest size.
> >
> > I recently discovered p7zip which comes with the LZMA compression algorithm,
> > which is somewhat better than gzip and bzip2 on most datasets, and I also
> > noticed that this tool provides support for gzip and bzip2 outputs. So I tried
> > to produce some of those standard outputs, and observed a slight gain compared
> > to the default tools. The reason is that we can change the number of passes and
> > the dictionnary size.
>
> Is it any smaller than a UPX'd kernel? (I think you need the beta version.
> I know the upx-ucl in debian won't compress but upx-ucl-beta will if you
> force). I got a significant reduction using it.
It's not better at all, but unfortunately, UPX cannot compress a kernel which
embeds a big initramfs. The problem is that the compressed initramfs is
embedded into vmlinux, which is then compressed into bzImage, and UPX only
replaces the bzImage compression.
May be it would work if we did not compress the initramfs before including
it into the vmlinux.
Willy
next prev parent reply other threads:[~2005-06-06 4: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 [this message]
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
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=20050606041101.GA14799@alpha.home.local \
--to=willy@w.ods.org \
--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.