From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux-crypto@vger.kernel.org,
squashfs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org
Subject: Re: [Squashfs-devel] [patch 0/3] [RFC] zlib crypto module
Date: Sat, 06 Sep 2008 05:41:03 +0100 [thread overview]
Message-ID: <48C209DF.5040509@lougher.demon.co.uk> (raw)
In-Reply-To: <20080829134158.108976037@vixen.sonytel.be>
Geert Uytterhoeven wrote:
> These patches add a (de)compression module for the "zlib" format using the
> crypto API:
> [1] crypto: Add a zlib crypto module
> [2] tcrypt: Add a self test for the zlib crypto module
> [3] squashfs: Switch from zlib/inflate to "zlib" crypto module
>
> The last patch is a proof-of-concept to make SquashFS 3.4 use this new zlib
> crypto module. This makes it easier to e.g. change the decompression algorithm
> in SquashFS or to make use of a hardware-accelerated zlib crypto module.
>
> It can be extended to other compressed file systems, like e.g. AxFS and CRAMFS.
>
> All comments are welcome. Thanks!
>
Moving Squashfs over to the crypto API is a good idea. When the zlib
crypto module code is in the mainline kernel moving Squashfs, AxFS and
CRAMFS over will be easy.
Are you planning to do the necessary work to get this (or a subsequent
version following the comments from Herbert Xu) into mainline?
Cheers
Phillip
prev parent reply other threads:[~2008-09-06 4:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 13:41 [patch 0/3] [RFC] zlib crypto module Geert Uytterhoeven
2008-08-29 13:41 ` [patch 1/3] crypto: Add a " Geert Uytterhoeven
2008-08-30 6:23 ` Herbert Xu
2008-08-30 6:39 ` David Woodhouse
2008-08-29 13:42 ` [patch 2/3] tcrypt: Add a self test for the " Geert Uytterhoeven
2008-08-29 13:42 ` [patch 3/3] squashfs: Switch from zlib/inflate to "zlib" " Geert Uytterhoeven
2008-09-06 4:41 ` Phillip Lougher [this message]
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=48C209DF.5040509@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=squashfs-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).