> > > > The crypto_alloc_shash will only identify cipher implementations that > were > > registered with the CRYPTO_ALG_TYPE_SHASH flag. That flag is set when a > cipher > > is registered using crypto_register_shash. > > > > Thus, ciphers registered with crypto_register_ahash will not bear this > flag > > and thus will not be found by the allocation function. > > is there a reason why we don't emulate the synchronous functionality > in the crypto API layer if a driver implements only the async interface? > > Or is it just a matter of -ENOPATCH? :) > Well, one reason might be that asynchronous implementations are usually hardware accelerators that rely on many operations being batch queued in order to actually usefully accelerate anything (due to large latencies). Which you can't do from the synchronous interface, so you'd get a slow down, not a speed up. (But some people - Ad :-) - might argue that using the accelerator may still be useful to offload the CPU, reduce power consumption, etc.) In any case, I didn't really know this but I'm quite happy with it. If you want *performance*, you shouldn't end up at a h/w accelerator with a synchronous API. If you do want the h/w acceleration, you can always use the asynchronous API, so nothing lost there, you do have a choice. Regards, Pascal van Leeuwen Silicon IP Architect, Multi-Protocol Engines @ Inside Secure www.insidesecure.com
