From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
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 11:01:23 +0100 [thread overview]
Message-ID: <10f740e80912100201l6d83588evff46e95ec96d0aed@mail.gmail.com> (raw)
In-Reply-To: <4B2042FA.8080406@lougher.demon.co.uk>
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 ;-)
In addition, using the Crypto API has the advantage that Squashfs will
use hardware decompression if/when available.
> Yes I did consider using the cryptoapi, but this doesn't have support for
> lzma in mainline.
IIRC, Felix Fietkau added support for that for OpenWRT...
> My aim is add lzma filesystem support to Squashfs using the existing kernel
> lzma iplementation, and to make as few changes to that as necessary.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2009-12-10 10:01 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 ` [PATCH 1/9] Squashfs: move zlib decompression wrapper code into a separate file 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 [this message]
2009-12-10 21:17 ` Phillip Lougher
2009-12-10 22:20 ` Felix Fietkau
2009-12-10 23:20 ` Phillip Lougher
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=10f740e80912100201l6d83588evff46e95ec96d0aed@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--cc=dedekind1@gmail.com \
--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=phillip@lougher.demon.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).