Re: [PATCHv4 3/7] crypto: sa2ul: add sha1/sha256/sha512 support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 30/06/2020 07:49, Herbert Xu wrote:
On Fri, Jun 26, 2020 at 12:15:42PM +0300, Tero Kristo wrote:

I have been experimenting with an alternate approach, where I have a small
buffer within the context, this would be more like the way other drivers do
this. If the buffer is closed before running out of space, I can push this
to be processed by HW, otherwise I must fallback to SW. Does this sound like
a better approach?

You can buffer up to a block obviously.  Anything beyond that
should just use a fallback.

Only up-to block size? This would limit the buffer to 64-128 bytes.

I was hoping I could cache data upto 1024 bytes at least in the context, as this would allow running certain openssl cases with hw accelerated crypto. Openssl speed test via cryptodev appears to do sha_init - sha_update - sha_final chain with any size data.

-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki



[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux