From: Jared Hulbert <jaredeh@gmail.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Phillip Lougher <phillip@lougher.demon.co.uk>
Subject: Re: [PATCH 5/5] squashfs: Make SquashFS 4 use the new pcomp crypto interface
Date: Wed, 18 Feb 2009 16:24:29 -0800 [thread overview]
Message-ID: <6934efce0902181624q57f3423dm50cda218781e4399@mail.gmail.com> (raw)
In-Reply-To: <1234972402-24298-6-git-send-email-Geert.Uytterhoeven@sonycom.com>
> Modify SquashFS 4 to use the new "pcomp" crypto interface for decompression,
> instead of calling the underlying zlib library directly. This simplifies e.g.
> the addition of support for hardware decompression and different decompression
> algorithms.
Geert,
When did this become an option? I thought zlib in the crypto
interface was not compatible with zlib. Is that not the case anymore?
Have you looked at AXFS enough to judge if this would be as easy a
job as it looks to convert?
How do you get from here to supporting alternate compressors?
next prev parent reply other threads:[~2009-02-19 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 15:53 [PATCH 0/5] Partial (de)compression Crypto API Geert Uytterhoeven
2009-02-18 15:53 ` [PATCH 1/5] crypto: compress - Add pcomp interface Geert Uytterhoeven
2009-02-18 15:53 ` [PATCH 2/5] crypto: testmgr - Add support for the " Geert Uytterhoeven
2009-02-18 15:53 ` [PATCH 3/5] crypto: new zlib crypto module, using pcomp Geert Uytterhoeven
2009-02-18 15:53 ` [PATCH 4/5] crypto: testmgr - add zlib test Geert Uytterhoeven
2009-02-18 15:53 ` [PATCH 5/5] squashfs: Make SquashFS 4 use the new pcomp crypto interface Geert Uytterhoeven
2009-02-19 0:24 ` Jared Hulbert [this message]
2009-02-19 13:42 ` Geert Uytterhoeven
2009-04-03 6:00 ` Jared Hulbert
2009-02-19 4:14 ` [PATCH 1/5] crypto: compress - Add pcomp interface Herbert Xu
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=6934efce0902181624q57f3423dm50cda218781e4399@mail.gmail.com \
--to=jaredeh@gmail.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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
all inboxes | Powered by JetHome®