mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: dedekind1@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
	linux-embedded@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, phillip.lougher@gmail.com,
	Tim Bird <tim.bird@am.sony.com>,
	Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Felix Fietkau <nbd@openwrt.org>
Subject: Re: [PATCH 1/9] Squashfs: move zlib decompression wrapper code into a 	separate file
Date: Thu, 10 Dec 2009 23:20:41 +0000	[thread overview]
Message-ID: <4B218249.4040501@lougher.demon.co.uk> (raw)
In-Reply-To: <10f740e80912100201l6d83588evff46e95ec96d0aed@mail.gmail.com>

Geert Uytterhoeven wrote:
> Hi Phillip,
> 
> On Thu, Dec 10, 2009 at 01:38, Phillip Lougher
> <phillip@lougher.demon.co.uk> wrote:
>> Artem Bityutskiy wrote:
>>> Did you consider using cryptoapi? UBIFS uses zlib/lzo in cryptoapi - it
>>> is a very clean way.
> 
> Exactly my question, as that's why the Crypto API was extended with
> support for partial (de)compression in the first place ;-)
> 

Your cryptoapi patches are on my "must do something about them" list, I've
not forgotten them :-)   The lack of lzma in the crypotapi made moving
solely to the cryptoapi difficult, when I wanted to add lzma decompression
support.

The decompressor framework is my _solution_ to this problem.  This allows
cryptoapi support to be added as additional decompression_wrapper, with
multiple compression types using the crptoapi wrapper as appropriate.
This has the advantage it allows Squashfs to use the cryptoapi (with
its advantages), without needlessly restricting Squashfs to the
compression algorithms supported by the cryptoapi.

Let's get this mainlined, and then we can work on getting your
cryptoapi patches integrated into that.  That'll make me happy,
and hopefully you'll be happy too?

Thanks

Phillip

  parent reply	other threads:[~2009-12-10 23:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NHTHg-0001sM-NQ@dylan.lougher.demon.co.uk>
2009-12-07 22:57 ` Andrew Morton
2009-12-08 22:20   ` Phillip Lougher
2009-12-09 10:00     ` Artem Bityutskiy
2009-12-10  0:38       ` Phillip Lougher
2009-12-10 10:01         ` Geert Uytterhoeven
2009-12-10 21:17           ` Phillip Lougher
2009-12-10 22:20             ` Felix Fietkau
2009-12-10 23:20           ` Phillip Lougher [this message]
2009-12-07  8:37 Phillip Lougher
  -- strict thread matches above, loose matches on Subject: below --
2009-12-07  8:25 root

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=4B218249.4040501@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=akpm@linux-foundation.org \
    --cc=dedekind1@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=phillip.lougher@gmail.com \
    --cc=tim.bird@am.sony.com \
    /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®