From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Lasse Collin <lasse.collin@tukaani.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Randy Dunlap <rdunlap@xenotime.net>,
qasdfgtyuiop <qasdfgtyuiop@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
alain@knaff.lu, albin.tonnerre@free-electrons.com
Subject: Re: [PATCH] kconfig: update compression algorithm info
Date: Wed, 18 Apr 2012 19:23:49 +0200 [thread overview]
Message-ID: <20120418172349.GA6165@x4> (raw)
In-Reply-To: <20120418200929.086ce3a7@tukaani.org>
On 2012.04.18 at 20:09 +0300, Lasse Collin wrote:
> On 2012-04-18 H. Peter Anvin wrote:
> > On 04/18/2012 09:40 AM, Lasse Collin wrote:
> > > - LZO should give the fastest boot from a hard disk (desktop
> > > systems where file size doesn't matter much).
> >
> > That really depends on the speed of your disk vs CPU.
>
> Yes. Maybe it isn't good to give so clear recommendation for LZO over
> gzip here.
>
> I think it is still safe to say that gzip and LZO are better than
> bzip2, XZ, or LZMA for compressing a kernel that will be loaded from a
> normal hard disk. It would be unusual if reading the disk was so slow
> that e.g. XZ would make the booting faster than gzip.
When btrfs will finally implement LZ4 compression this would be the obvious
candidate for the fastest boot algo, because its decompression speed is
amazing.
For example here is a comparison with LZO on boot/compressed/vmlinux.bin:
memcpy = 75 ms (10251 MB/s), 13436968->13436968
Codec version args Size (Ratio) C.Speed D.Speed
LZ4 r59 12 4952064 (x 2.71) C: 518 MB/s D:1472 MB/s
LZO 2.05 1x1 4825088 (x 2.78) C: 472 MB/s D: 504 MB/s
--
Markus
next prev parent reply other threads:[~2012-04-18 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 10:19 Small and unimportant description mistakes of Kernel compression mode in kernel config qasdfgtyuiop
2012-03-28 0:04 ` Tilman Schmidt
2012-04-17 23:13 ` [PATCH] kconfig: update compression algorithm info Randy Dunlap
2012-04-18 16:40 ` Lasse Collin
2012-04-18 16:45 ` H. Peter Anvin
2012-04-18 17:09 ` Lasse Collin
2012-04-18 17:23 ` Markus Trippelsdorf [this message]
2012-04-18 17:29 ` H. Peter Anvin
2012-04-18 17:36 ` Markus Trippelsdorf
2012-04-18 17:25 ` H. Peter Anvin
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=20120418172349.GA6165@x4 \
--to=markus@trippelsdorf.de \
--cc=akpm@linux-foundation.org \
--cc=alain@knaff.lu \
--cc=albin.tonnerre@free-electrons.com \
--cc=hpa@zytor.com \
--cc=lasse.collin@tukaani.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qasdfgtyuiop@gmail.com \
--cc=rdunlap@xenotime.net \
/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