Hi, Ok... But normally kernel client code uses sync API as shash. And I provide async hw driver via async ahash API. That is simply will not be used at all. Client must be changed to use async ahash API in order to benefit from HW crypto. Right? Thanks, Dmitry ext Herbert Xu wrote: > Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx> wrote: > >> One interesting issue >> >> Many clients in the kernel set CRYPTO_TFM_REQ_MAY_SLEEP to desc.flags. >> It is used by crypto_yeld(). >> > > That flag is really only meaningful for synchronous implementations. > > For hardware crypto that is asynchronous, you can simply ignore it > in most cases (exceptions include invoking a syncrhonous backup, for > example). > > Cheers, > -- 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
