From: Dan Malek <dan@embeddededge.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Colin.Helliwell@Zarlink.Com, linux-mips@linux-mips.org
Subject: Re: Compressed kernels
Date: Thu, 20 Nov 2003 16:42:07 -0500 [thread overview]
Message-ID: <3FBD352F.6020103@embeddededge.com> (raw)
In-Reply-To: 20031120210257.GA758@linux-mips.org
Ralf Baechle wrote:
> Compressed kernels seem to be fairly high on everybody's list. Due to
> size limits of some boatloaders and flash memory being always too small
> and too expensive I guess there would also be some interest in bzip2
> support.
Interesting thought. I compressed the binary image using bzip2 instead
of gzip, found it was only about 7% smaller (approximately 60K bytes).
To this, we have to add the trade off that the kernel already contains
too many versions of a readily available zlib, and the attached initrd
is also a gzip file. Five years ago we used to be concerned about a
few bytes here and there, which prompted the interest in compressed
kernels, but today the embedded systems I'm working with have lots of
flash memory. It seems product development cost to add a little more
flash is winning over spending the engineering time to squeeze those
last few bytes.
I don't think I'll spend my time doing it, but the process of creating
the compressed image and the calls to the uncompress functions are very
clear if someone else wants to do it :-)
Thanks.
-- Dan
next prev parent reply other threads:[~2003-11-20 21:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 9:10 Compressed kernels Colin.Helliwell
2003-11-20 15:21 ` Dan Malek
2003-11-20 21:02 ` Ralf Baechle
2003-11-20 21:42 ` Dan Malek [this message]
2003-11-20 22:33 ` Wolfgang Denk
2003-11-20 22:50 ` Dan Malek
2003-11-25 23:44 ` Ralf Baechle
2003-11-22 2:41 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2005-03-31 8:35 Compressed Kernels JP Foster
2005-03-31 8:42 ` Robin H. Johnson
2005-03-31 16:24 ` Pete Popov
2005-04-01 9:05 ` JP
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=3FBD352F.6020103@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Colin.Helliwell@Zarlink.Com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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