From: Herbert Xu <herbert@gondor.apana.org.au>
To: abed mohammad kamaluddin <abedamu@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: algif for compression?
Date: Sat, 10 Dec 2016 16:10:14 +0800 [thread overview]
Message-ID: <20161210081014.GA32746@gondor.apana.org.au> (raw)
In-Reply-To: <CACVarETuTx40WFD5TRUCwiYv5r3SEvhuJHpGjqPsz90qVZsYKA@mail.gmail.com>
abed mohammad kamaluddin <abedamu@gmail.com> wrote:
>
> We are also looking for user-space access to the kernel crypto layer
> compression algorithms. I have gone through AF_ALG but couldn’t find
> support for compression ops through it. This is required for our
> hardware zip engines whose driver hooks up to the crypto layer.
>
> I was going through the lists and stumbled across this thread. Has
> there been any updates or efforts put up in this direction since this
> thread is a few years old. If not, are there any alternate
> implementations that allow user-space access to compression? I have
> gone through cryptodev and see the same limitation there.
>
> Would appreciate any pointers in this regard.
The compression interface is currently in a state of flux. We
should make it settle down first before exporting it to user-space.
For a start it would be good to actually switch IPsec/IPcomp over
to the new compression interface.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2016-12-10 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 19:57 algif for compression? abed mohammad kamaluddin
2016-12-10 8:10 ` Herbert Xu [this message]
2016-12-16 14:11 ` abed mohammad kamaluddin
2016-12-21 8:52 ` Herbert Xu
2017-04-03 6:10 ` abed mohammad kamaluddin
2017-04-03 7:26 ` Stephan Müller
2017-04-03 8:41 ` abed mohammad kamaluddin
-- strict thread matches above, loose matches on Subject: below --
2014-03-14 18:05 Dan Streetman
2014-04-03 12:41 ` Herbert Xu
2014-04-03 18:03 ` Dan Streetman
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=20161210081014.GA32746@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=abedamu@gmail.com \
--cc=linux-crypto@vger.kernel.org \
/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).