From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] crypto: algif_hash - User-space interface for hash operations
Date: Thu, 04 Nov 2010 12:23:19 -0700 (PDT) [thread overview]
Message-ID: <20101104.122319.183032357.davem@davemloft.net> (raw)
In-Reply-To: <E1PE3jX-0000MX-UB@gondolin.me.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu, 04 Nov 2010 12:36:19 -0500
> crypto: algif_hash - User-space interface for hash operations
>
> This patch adds the af_alg plugin for hash, corresponding to
> the ahash kernel operation type.
>
> Keys can optionally be set through the setsockopt interface.
>
> Each sendmsg call will finalise the hash unless sent with a MSG_MORE
> flag.
>
> Partial hash states can be cloned using accept(2).
>
> The interface is completely synchronous, all operations will
> complete prior to the system call returning.
>
> Both sendmsg(2) and splice(2) support reading the user-space
> data directly without copying (except that the Crypto API itself
> may copy the data if alignment is off).
>
> For now only the splice(2) interface supports performing digest
> instead of init/update/final. In future the sendmsg(2) interface
> will also be modified to use digest/finup where possible so that
> hardware that cannot return a partial hash state can still benefit
> from this interface.
>
> Thakns to Miloslav Trmac for reviewing this and contributing
> fixes and improvements.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2010-11-04 19:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 8:42 RFC: Crypto API User-interface Herbert Xu
2010-09-07 9:18 ` Tomas Mraz
2010-09-07 14:06 ` Christoph Hellwig
2010-09-07 14:11 ` Herbert Xu
2010-09-07 14:24 ` Christoph Hellwig
2010-09-07 14:39 ` Herbert Xu
2010-09-07 14:49 ` Nikos Mavrogiannopoulos
2010-09-07 14:57 ` Nikos Mavrogiannopoulos
2010-09-07 14:59 ` Christoph Hellwig
2010-10-19 13:44 ` Herbert Xu
2010-10-20 10:24 ` Nikos Mavrogiannopoulos
2010-11-04 17:34 ` Herbert Xu
2010-11-04 17:36 ` [PATCH 1/4] net - Add AF_ALG macros Herbert Xu
2010-11-04 19:22 ` David Miller
2010-11-04 17:36 ` [PATCH 3/4] crypto: algif_hash - User-space interface for hash operations Herbert Xu
2010-11-04 19:23 ` David Miller [this message]
2010-11-04 17:36 ` [PATCH 2/4] crypto: af_alg - User-space interface for Crypto API Herbert Xu
2010-11-04 19:23 ` David Miller
2010-11-04 17:36 ` [PATCH 4/4] crypto: algif_skcipher - User-space interface for skcipher operations Herbert Xu
2010-11-04 19:23 ` David Miller
2010-10-19 13:46 ` [PATCH 1/4] net - Add AF_ALG macros Herbert Xu
2010-10-20 9:01 ` David Miller
2010-10-19 13:46 ` [PATCH 2/4] crypto: af_alg - User-space interface for Crypto API Herbert Xu
2010-10-19 13:46 ` [PATCH 4/4] crypto: algif_skcipher - User-space interface for skcipher operations Herbert Xu
2010-10-19 13:46 ` [PATCH 3/4] crypto: algif_hash - User-space interface for hash operations 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=20101104.122319.183032357.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).