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 07:07:43 -0400 [thread overview]
Message-ID: <20050606110743.GA23107@animx.eu.org> (raw)
In-Reply-To: <20050606041101.GA14799@alpha.home.local>
Keep me CC.
Willy Tarreau wrote:
> On Sun, Jun 05, 2005 at 09:02:46PM -0400, Wakko Warner wrote:
> > 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.
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.
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2005-06-06 11:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 22:35 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 [this message]
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=20050606110743.GA23107@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 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®