[dm-devel] [PATCH] DM-CRYPT: Scale to multiple CPUs

Milan Broz mbroz at redhat.com
Mon May 31 18:55:50 UTC 2010


On 05/31/2010 08:27 PM, Andi Kleen wrote:

>>> AES-NI is not asynchronous and doesn't have limited resources.
>>
>> AES-NI used asynchronous crypto interface, was using asynchronous
>> crypto API cryptd daemon IIRC. So this changed?
> 
> AFAIK all ciphers use the asynchronous interface,  but that 
> doesn't mean they are actually asynchronous. AES-NI certainly
> does not require running in a special thread. The only
> thing it doesn't support is running from interrupt context.

I mean how it is implemented now in crypto API, and I was almost
sure that aes-ni acceleration code uses cryptd (iow real asynchronous processing)
and also that not all CPU cores can run these instruction in parallel.

So I am mistaken here?

Milan




More information about the dm-devel mailing list