From: "H. Peter Anvin" <hpa@zytor.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Lasse Collin <lasse.collin@tukaani.org>,
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 10:29:07 -0700 [thread overview]
Message-ID: <4F8EF9E3.7030801@zytor.com> (raw)
In-Reply-To: <20120418172349.GA6165@x4>
On 04/18/2012 10:23 AM, Markus Trippelsdorf wrote:
>
> When btrfs will finally implement LZ4 compression this would be the obvious
> candidate for the fastest boot algo, because its decompression speed is
> amazing.
>
Uh, no (and what does btrfs have to do with anything here?)
The issue is that the ratio of I/O speed to CPU can mean that a slower
decompression algorithm with better compression can still win,
time-wise, if your media is slow and your CPU is fast.
-hpa
next prev parent reply other threads:[~2012-04-18 17:29 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
2012-04-18 17:29 ` H. Peter Anvin [this message]
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=4F8EF9E3.7030801@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=alain@knaff.lu \
--cc=albin.tonnerre@free-electrons.com \
--cc=lasse.collin@tukaani.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--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