> Would it be possible to make CPU-affinity configurable for *single* > kcryptd instances? Either in the way to nail a specific kcryptd to a > specific CPU or (what would be better for me, I guess) in the way to > completely remove CPU-affinity from a specific kcryptd, like it was > before? I don't think that's a good idea. You probably need to find some way to make pcrypt (parallel crypt layer) work for dmcrypt. That may actually give you more speedup too than your old hack because it can balance over more cores. Or get a system with AES-NI -- that usually solves it too. Frankly I don't think it's a very interesting case, the majority of workloads are not like that. -Andi _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
