On Mon, May 31, 2010 at 09:04:00PM +0200, Andi Kleen wrote: > > 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. Right. The only reason aes-ni uses the async interface is to work around the fact that you have to save FPU state when using it. For dm-crypt you can consider it to be synchronous. Note that cryptd is nothing like pcrypt. cryptd always keeps the work on the local CPU, even if goes into another thread. OTOH pcrypt was designed to parallelise the work across CPUs. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
