> 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. I think you can configure it to use cryptd (or pcrypt), but it's not default and usually higher overhead. Each CPU core has its own support for AES-NI (it's part of the SSE units), there's no shared crypto hardware between cores. There are other systems with separate AES units, but they are considerably more obscure. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
