From: Pavel Vasilyev <pavel@pavlinux.ru>
To: Lasse Collin <lasse.collin@tukaani.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] Decompressors: Add boot-time XZ support
Date: Sat, 11 Dec 2010 00:58:13 +0300 [thread overview]
Message-ID: <4D02A275.1060308@pavlinux.ru> (raw)
In-Reply-To: <fYgcy-12E-3@gated-at.bofh.it>
On 10.12.2010 21:50, Lasse Collin wrote:
> From: Lasse Collin <lasse.collin@tukaani.org>
[--- ням ---]
>
> +config KERNEL_XZ
> + bool "XZ"
> + depends on HAVE_KERNEL_XZ
> + help
> + XZ uses the LZMA2 algorithm and instruction set specific
> + BCJ filters which can improve compression ratio of executable
> + code. The size of the kernel is about 30% smaller with XZ in
> + comparison to gzip. On architectures for which there is a BCJ
> + filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ
> + will create a few percent smaller kernel than plain LZMA.
> +
> + The speed is about the same as with LZMA: The decompression
> + speed of XZ is better than that of bzip2 but worse than gzip
> + and LZO. Compression is slow.
> +
> config KERNEL_LZO
> bool "LZO"
> depends on HAVE_KERNEL_LZO
Not worked without this:
--- кусь ---
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index e330da2..d27a9c7 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -52,6 +52,7 @@ config X86
select HAVE_KERNEL_BZIP2
select HAVE_KERNEL_LZMA
select HAVE_KERNEL_LZO
+ select HAVE_KERNEL_XZ
select HAVE_HW_BREAKPOINT
select HAVE_MIXED_BREAKPOINTS_REGS
select PERF_EVENTS
--- кусь ---
.... and for other archs needed.
next parent reply other threads:[~2010-12-10 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fVmRb-eH-7@gated-at.bofh.it>
[not found] ` <fYgcy-12E-3@gated-at.bofh.it>
2010-12-10 21:58 ` Pavel Vasilyev [this message]
2010-12-10 22:23 ` Lasse Collin
2010-12-02 19:14 [PATCH v2 RFC 2/3] " Lasse Collin
2010-12-10 18:45 ` [PATCH v3] " Lasse Collin
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=4D02A275.1060308@pavlinux.ru \
--to=pavel@pavlinux.ru \
--cc=lasse.collin@tukaani.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®