From: Tero Kristo <t-kristo@ti.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <davem@davemloft.net>, <linux-crypto@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <j-keerthy@ti.com>
Subject: Re: [PATCHv4 3/7] crypto: sa2ul: add sha1/sha256/sha512 support
Date: Tue, 30 Jun 2020 11:17:30 +0300 [thread overview]
Message-ID: <17db9cc3-26a0-bb90-4b35-f675fecb640f@ti.com> (raw)
In-Reply-To: <20200630075951.GA3977@gondor.apana.org.au>
On 30/06/2020 10:59, Herbert Xu wrote:
> On Tue, Jun 30, 2020 at 10:58:28AM +0300, Tero Kristo wrote:
>>
>> Openssl uses init->update->final sequencing, and it would be nice to have
>> this use crypto accelerator. Otherwise we basically support cipher
>> acceleration from openssl, but not hashing.
>
> You're referring to algif_hash, right? If so it'd be much easier
> to implement the buffering in user-space.
algif_hash / cryptodev can both be used via openssl, but I think both of
them have the same limitation, yeah.
Anyways, sounds like you prefer dropping any hacks towards this from the
kernel driver, so I'll just do that and consider patching the upper
layers for openssl maybe...
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2020-06-30 8:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 7:14 [PATCHv4 0/7] crypto: sa2ul support for TI K3 SoCs Tero Kristo
2020-06-15 7:14 ` [PATCHv4 1/7] dt-bindings: crypto: Add TI SA2UL crypto accelerator documentation Tero Kristo
2020-06-15 7:14 ` [PATCHv4 2/7] crypto: sa2ul: Add crypto driver Tero Kristo
2020-06-15 7:14 ` [PATCHv4 3/7] crypto: sa2ul: add sha1/sha256/sha512 support Tero Kristo
2020-06-26 4:31 ` Herbert Xu
2020-06-26 9:15 ` Tero Kristo
2020-06-30 4:49 ` Herbert Xu
2020-06-30 7:20 ` Tero Kristo
2020-06-30 7:46 ` Herbert Xu
2020-06-30 7:52 ` Tero Kristo
2020-06-30 7:54 ` Herbert Xu
2020-06-30 7:58 ` Tero Kristo
2020-06-30 7:59 ` Herbert Xu
2020-06-30 8:17 ` Tero Kristo [this message]
2020-06-15 7:14 ` [PATCHv4 4/7] crypto: sa2ul: Add AEAD algorithm support Tero Kristo
2020-06-15 7:14 ` [PATCHv4 5/7] crypto: sa2ul: add device links to child devices Tero Kristo
2020-06-15 7:14 ` [PATCHv4 6/7] arm64: dts: ti: k3-am6: Add crypto accelarator node Tero Kristo
2020-06-15 7:14 ` [PATCHv4 7/7] arm64: dts: ti: k3-j721e-main: Add crypto accelerator node Tero Kristo
2020-06-15 18:20 ` [PATCHv4 0/7] crypto: sa2ul support for TI K3 SoCs Eric Biggers
2020-06-16 4:24 ` Tero Kristo
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=17db9cc3-26a0-bb90-4b35-f675fecb640f@ti.com \
--to=t-kristo@ti.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).