From: alexander.stein@systec-electronic.com (Alexander Stein)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: add support for uncompressed uImage kernel
Date: Thu, 18 Nov 2010 08:38:26 +0100 [thread overview]
Message-ID: <201011180838.26679.alexander.stein@systec-electronic.com> (raw)
In-Reply-To: <AANLkTi=6OE=50EExgkay2ycuSPFsOp4E-RmxkNktK_Xk@mail.gmail.com>
Soory for late answer,
On Saturday 13 November 2010, 11:47:41 Albin Tonnerre wrote:
> <linux@arm.linux.org.uk> wrote:
> > Is it really faster to copy an uncompressed image than it is to
> > decompress using LZMA with caches on?
>
> In my experience, using LZMA is painfully slow on older ARM CPUs.
>
> If you really need to boot quickly you might want to try LZO, which
> should give you results close to the uncompressed performance. It
> might still be slower though, especially if you're able to load your
> kernel image to memory fairly quickly
We only have experience with GZIP. Our compressed kernel is ~1,8MB and
uncompressed ~4MB.
On an AT91 ARM9 SoC the decompression takes about 1-2s of time. Caches should
be disabled, as far as I could see in decompression code.
Copying the uncompressed kernel from NOR to SD-RAM takes about 140ms. So if
you can afford the additional storage need, simply copying the uncompressed
kernel is much faster than copying the compressed kernel which decompresses
itself.
Best regards,
Alexander
next prev parent reply other threads:[~2010-11-18 7:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 13:50 [PATCH] ARM: add support for uncompressed uImage kernel Alexander Stein
2010-11-09 14:04 ` Russell King - ARM Linux
2010-11-09 14:51 ` Uwe Kleine-König
2010-11-09 22:38 ` Sascha Hauer
2010-11-13 10:47 ` Albin Tonnerre
2010-11-18 7:38 ` Alexander Stein [this message]
2010-11-18 8:15 ` Uwe Kleine-König
2010-11-18 9:10 ` Russell King - ARM Linux
2010-11-18 10:18 ` Alexander Stein
2010-11-09 14:57 ` Uwe Kleine-König
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=201011180838.26679.alexander.stein@systec-electronic.com \
--to=alexander.stein@systec-electronic.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).