From: Lasse Collin <lasse.collin@tukaani.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: 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, hpa@zytor.com
Subject: Re: [PATCH] kconfig: update compression algorithm info
Date: Wed, 18 Apr 2012 19:40:55 +0300 [thread overview]
Message-ID: <20120418194055.2d929e58@tukaani.org> (raw)
In-Reply-To: <4F8DF90B.1090002@xenotime.net>
On 2012-04-17 Randy Dunlap wrote:
> There have been new compression algorithms added without
> updating nearby relevant descriptive text that refers to
> (a) the number of compression algorithms and (b) the most
> recent one. Fix these inconsistencies.
It could also be good to fix which algo has the best compression ratio.
XZ supports BCJ filters on some archs and on those it will give a few
percent smaller kernel than LZMA. Without BCJ, XZ and LZMA are
practically tied.
If you feel like it, maybe it would be nice to have some
recommendations in the descriptions:
- gzip is a safe choice if unsure what to do.
- XZ is good when small size is important (embedded systems,
live CDs).
- LZO should give the fastest boot from a hard disk (desktop systems
where file size doesn't matter much).
--
Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
next prev parent reply other threads:[~2012-04-18 16:41 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 [this message]
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
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=20120418194055.2d929e58@tukaani.org \
--to=lasse.collin@tukaani.org \
--cc=akpm@linux-foundation.org \
--cc=alain@knaff.lu \
--cc=albin.tonnerre@free-electrons.com \
--cc=hpa@zytor.com \
--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
Powered by JetHome