It is pointless to track the submitting CPU.
No you are wrong.
For what? For avoiding cache bounces? But the encrypting is
order-of-magnitude slower than memory speed.
On a system with reasonably fast CPUs it's fastest to just stay
on your current CPU, don't try to talk to other CPUs, avoid
communication, just get the work done ASAP. But make
sure you can do this on multiple CPUs at the same time.
With AES-NI this becomes even more pronounced because it effectively
makes the CPU faster for encryption.
-andi
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
