Thread (19 messages) 19 messages, 4 authors, 2012-06-20

Re: [PATCH] crypto: serpent - add x86_64/avx assembler implementation

From: Jussi Kivilinna <hidden>
Date: 2012-05-30 18:53:39
Also in: lkml

Possibly related (same subject, not in this thread)

Quoting Andi Kleen [off-list ref]:
quoted
I agree with that. Currently when I boot my PC with a new 3.4 kernel all the
ciphers from the intel-aesni module get loaded whether I need them  
or not. As
Jussi stated most people using distros probably won't need the
serpent-avx-x86_64 module get loaded automatically, so it's  
probably better to
leave it that way.
That means you got a 50% chance to use the wrong serpent.

This was a continuous problem with AESNI and the accelerated CRC,
that is why the cpuid probing was implemented.

Without some form of auto probing you may as well not bother with
the optimization.

-Andi
Hm.. should not the i586/x86_64 assembler implementations of AES etc  
be autoloaded then too?

-Jussi
--
ak@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help