linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Lasse Collin <lasse.collin@tukaani.org>
Cc: linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>, Alain Knaff <alain@knaff.lu>,
	Albin Tonnerre <albin.tonnerre@free-electrons.com>,
	Phillip Lougher <phillip@lougher.demon.co.uk>
Subject: Re: [PATCH RFC 1/3] Decompressors: Add XZ decompressor module
Date: Wed, 24 Nov 2010 14:25:49 -0800	[thread overview]
Message-ID: <20101124142549.c1b9ad14.akpm@linux-foundation.org> (raw)
In-Reply-To: <201011242251.52927.lasse.collin@tukaani.org>

On Wed, 24 Nov 2010 22:51:52 +0200
Lasse Collin <lasse.collin@tukaani.org> wrote:

> From: Lasse Collin <lasse.collin@tukaani.org>
> 
> In userspace, the .lzma format has become mostly a legacy
> file format that got superseded by the .xz format. Similarly,
> LZMA Utils was superseded by XZ Utils.
> 
> These patches add support for XZ decompression into
> the kernel. Most of the code is as is from XZ Embedded
> <http://tukaani.org/xz/embedded.html>. It was written for
> the Linux kernel but is usable in other projects too.
> 
> Advantages of XZ over the current LZMA code in the kernel:
>   - Nice API that can be used by other kernel modules; it's
>     not limited to kernel, initramfs, and initrd decompression.
>   - Integrity check support (CRC32)
>   - BCJ filters improve compression of executable code on
>     certain architectures. These together with LZMA2 can
>     produce a few percent smaller kernel or Squashfs images
>     than plain LZMA without making the decompression slower.
> 
> This patch: Add the main decompression code (xz_dec), testing
> module (xz_dec_test), wrapper script (xz_wrap.sh) for the xz
> command line tool, and documentation. The xz_dec module is
> enough to have a usable XZ decompressor e.g. for Squashfs.

I'm not seeing any documentation which tells me how to create, install
and execute xs-compressed kernels. There are new makefile targets?

>
> ...
>
> +#define bcj_x86_test_msbyte(b) ((b) == 0x00 || (b) == 0xFF)

This should be written in C.  It looks nicer, and so
bcj_x86_test_msbyte(*p++) won't explode.

> +static noinline_for_stack size_t bcj_x86(

hm, but it uses little stack space.

> +static noinline_for_stack size_t bcj_x86(
> +		struct xz_dec_bcj *s, uint8_t *buf, size_t size)

The preferred style is

static noinline_for_stack size_t bcj_x86(struct xz_dec_bcj *s, uint8_t *buf,
					size_t size)

or

static noinline_for_stack size_t
bcj_x86(struct xz_dec_bcj *s, uint8_t *buf, size_t size)

(lots of dittoes)

  reply	other threads:[~2010-11-24 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 20:51 [PATCH RFC 1/3] Decompressors: Add XZ decompressor module Lasse Collin
2010-11-24 22:25 ` Andrew Morton [this message]
2010-11-24 22:50   ` H. Peter Anvin
2010-11-24 22:51     ` H. Peter Anvin
2010-11-25 14:34   ` 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=20101124142549.c1b9ad14.akpm@linux-foundation.org \
    --to=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-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillip@lougher.demon.co.uk \
    /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;
as well as URLs for NNTP newsgroup(s).