|
|
|
Re: CRYPTO_ALG_ASYNC | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
On Thu, May 10, 2012 at 1:47 PM, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> 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 the async API you can still request for a sync implementation. What I can see this flag is not tested and used. Where is the place of code where it "returns" sync implementation? - Dmitry > > Cheers, > -- > Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html