From: Aras Vaichas <arasv@magellan-technology.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] bzip2 very slow
Date: Fri, 08 Apr 2005 13:34:18 +1000 [thread overview]
Message-ID: <4255FBBA.9020508@magellan-technology.com> (raw)
I recently started using bzip2 to compress my kernel, I made the necessary
changes in u-boot-1.1.2 to include bzip2 and increase the malloc size to 4MB.
The decompression for the bzip2 image is over 10 times slower compared to the
gzip image.
version: U-Boot-1.1.2 - 5338372 Feb 25 10:47 u-boot-1.1.2.tar.bz2
cpu: at91rm9200
from at91rm9200dk.h:
#define CONFIG_BZIP2 1
#define CFG_MALLOC_LEN (0x410000)
Here is a comparison of gzip vs bzip2 on the same 2.6.x kernel:
== gzip ==
$ gzip -v9 linux.bin
$ /usr/local/uboot/mkimage -A arm -O linux -C gzip -a 0x20008000 -e 0x20008000
-d linux.bin.gz uImage-2.6-dk
compressed file size: 877kB
decompression time: about 3 seconds
== bzip2 ==
$ bzip2 --best linux.bin
$ /usr/local/uboot/mkimage -A arm -O linux -C bzip2 -a 0x20008000 -e 0x20008000
-d linux.bin.bz2 uImage-2.6-dk
compressed file size: 813kB
decompression time: about 30 seconds
bzip2 is taking over 10 times longer to decompress for a 64K smaller file size.
Is this normal?
regards,
Aras Vaichas
reply other threads:[~2005-04-08 3:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4255FBBA.9020508@magellan-technology.com \
--to=arasv@magellan-technology.com \
--cc=u-boot@lists.denx.de \
/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