All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Albin Tonnerre <albin.tonnerre@free-electrons.com>
Cc: akpm@linux-foundation.org, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] Add support for LZO-compressed kernels
Date: Fri, 13 Nov 2009 15:45:13 +0000	[thread overview]
Message-ID: <20091113154513.GD27752@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1257942478-18719-2-git-send-email-albin.tonnerre@free-electrons.com>

On Wed, Nov 11, 2009 at 01:27:55PM +0100, Albin Tonnerre wrote:
> This is the first part of the lzo patch
> The lzo compressor is worse than gzip at compression, but faster at
> extraction. Here are some figures for an ARM board I'm working on:
> 
> Uncompressed size: 3.24Mo
> gzip  1.61Mo 0.72s
> lzo   1.75Mo 0.48s

>From my testing on a Cortex A9 model:
- lzo decompressor is 65% of the time gzip takes to decompress a kernel
- lzo kernel is 9% larger than a gzip kernel

which I'm happy to say confirms your figures when comparing the two.

However, when comparing your new gzip code to the old gzip code:
- new is 99% of the size of the old code
- new takes 42% of the time to decompress than the old code

What this means is that for a proper comparison, the results get even better:
- lzo is 7.5% larger than the old gzip'd kernel image
- lzo takes 28% of the time that the old gzip code took

So the expense seems definitely worth the effort.  The only reason I
can think of ever using gzip would be if you needed the additional
compression (eg, because you have limited flash to store the image.)

I would argue that the default for ARM should therefore be LZO.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  parent reply	other threads:[~2009-11-13 15:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 12:27 [PATCH v3 0/4] Add support for LZO-compressed kernel images Albin Tonnerre
2009-11-11 12:27 ` [PATCH v3 1/4] Add support for LZO-compressed kernels Albin Tonnerre
2009-11-11 12:27   ` [PATCH v3 2/4] Add support for LZO-compressed kernels for ARM Albin Tonnerre
2009-11-11 12:27     ` [PATCH v3 3/4] Add support for LZO-compressed kernels on x86 Albin Tonnerre
2009-11-11 12:27       ` [PATCH v3 4/4] Add LZO compression support for initramfs and old-style initrd Albin Tonnerre
2009-11-12 12:59     ` [PATCH v3 2/4] Add support for LZO-compressed kernels for ARM Martin Michlmayr
2009-11-13 14:29       ` Sebastian Andrzej Siewior
2009-11-13 14:50         ` Martin Michlmayr
2009-11-13 14:54           ` Albin Tonnerre
2009-11-13 15:21             ` Russell King
2009-11-13 15:52               ` Martin Michlmayr
2009-11-13 17:19                 ` Albin Tonnerre
2009-11-12 21:06     ` Martin Michlmayr
2009-11-12 21:06       ` Martin Michlmayr
2009-11-11 14:11   ` [PATCH v3 1/4] Add support for LZO-compressed kernels Wu Zhangjin
2009-11-12 22:33   ` Andrew Morton
2009-11-12 22:43     ` Albin Tonnerre
2009-11-13 15:45   ` Russell King [this message]
2009-11-12 22:25 ` [PATCH v3 0/4] Add support for LZO-compressed kernel images Russell King

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=20091113154513.GD27752@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=albin.tonnerre@free-electrons.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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 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.