On Sat, 2010-03-13 at 20:28 +0800, Herbert Xu wrote: > Pavel Roskin <proski@xxxxxxx> wrote: > > > > However, it's disappointing that the caller needs to deal explicitly > > with completions. The blkcipher API is much simpler. I would have hard > > time advocating a patch to CCMP that makes the code more complicated. > > You won't have to deal with completions if you allocate your > algorithm with the CRYPTO_ALG_ASYNC bit off. Of course you won't > be able to use most hardware accelerations either. Actually, I thought using CRYPTO_ALG_ASYNC in the mask meant to _exclude_ asynchronous algorithms. Is there any documentation for Linux crypto API that documents use of CRYPTO_ALG_ASYNC? Also, I'd like to know meanings of CRYPTO_TFM_REQ_MAY_BACKLOG and CRYPTO_TFM_REQ_MAY_SLEEP. The crypto API feels like a minefield to me - I should check everything in the code or even experiment to figure out how the public API works. -- Regards, Pavel Roskin -- 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
