On Thu, May 10, 2012 at 1:47 PM, Herbert Xu wrote:
> On Thu, May 10, 2012 at 01:31:10PM +0300, Kasatkin, Dmitry wrote:
>>
>> But why do we need it for AHASH or ABLKCIPHER?
>> It is obvious without it that they can be async?
>
> It makes sense for ahash/ablkcipher since even though you're
> using t
On Thu, May 10, 2012 at 01:31:10PM +0300, Kasatkin, Dmitry wrote:
>
> But why do we need it for AHASH or ABLKCIPHER?
> It is obvious without it that they can be async?
It makes sense for ahash/ablkcipher since even though you're
using the async API you can still request for a sync implementation.
On Thu, May 10, 2012 at 1:16 PM, Herbert Xu wrote:
> On Thu, May 10, 2012 at 12:33:40PM +0300, Kasatkin, Dmitry wrote:
>> Hello Herbert,
>>
>> CRYPTO_ALG_ASYNC is heavily used like:
>>
>> crypto_alloc_shash(hash_alg, 0, CRYPTO_ALG_ASYNC);
>
> Where did you see that? There is no need to specify
On Thu, May 10, 2012 at 12:33:40PM +0300, Kasatkin, Dmitry wrote:
> Hello Herbert,
>
> CRYPTO_ALG_ASYNC is heavily used like:
>
> crypto_alloc_shash(hash_alg, 0, CRYPTO_ALG_ASYNC);
Where did you see that? There is no need to specify ASYNC in the
mask for shash since they're always synchronou
