On Fri, Sep 27, 2019 at 09:58:14AM +0000, Pascal Van Leeuwen wrote: > > But I can see the appeal of getting a "done" response on the _encrypt()/ > _decrypt() call and then being able to immediately continue processing > the result data and having the async response handling separated off. This is how it works today. If your request can be fulfilled right away, you will get a return value other than EINPROGRESS and you just carry on, the completion callback never happens in this case. aesni-intel makes heavy use of this. In most cases it is sync. It only goes async when the FPU is not available. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt