linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Streetman <ddstreet@ieee.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: algif for compression?
Date: Thu, 3 Apr 2014 14:03:30 -0400	[thread overview]
Message-ID: <CALZtONA3xqBG=6n0UERJ=Ve7DEH1P5ZVu5C_dRN0Tt324MjvFw@mail.gmail.com> (raw)
In-Reply-To: <20140403124136.GA32279@gondor.apana.org.au>

On Thu, Apr 3, 2014 at 8:41 AM, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> Dan Streetman <ddstreet@ieee.org> wrote:
>> I see the algif_hash and algif_blkcipher implementations to allow
>> userspace AF_ALG socket access to kernel blkcipher and hash
>> algorithms, but has anyone done a algif_compression to allow userspace
>> access to compression algs?  I'm asking specifically wrt the 842
>> crypto module, which uses the hardware compression coprocessors on
>> newer powerpc systems.
>>
>> If not, is there any reason against adding a algif_compression to
>> provide the access?
>
> For a start nx-842 isn't even hooked into the crypto layer so
> there is no chance of exporting it through algif as is.

Wait, isn't it?  The crypto/842.c driver connects right to it.  Well,
it connects to the compression part of it, but that's the only part
I'm looking at exporting to userspace right now.



> There is no reason why you couldn't add it of course but that'd
> be a first step.
>
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-04-03 18:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 18:05 algif for compression? Dan Streetman
2014-04-03 12:41 ` Herbert Xu
2014-04-03 18:03   ` Dan Streetman [this message]
2016-12-07 19:57 abed mohammad kamaluddin
2016-12-10  8:10 ` Herbert Xu
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

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='CALZtONA3xqBG=6n0UERJ=Ve7DEH1P5ZVu5C_dRN0Tt324MjvFw@mail.gmail.com' \
    --to=ddstreet@ieee.org \
    --cc=herbert@gondor.apana.org.au \
    --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).