Is it necessary to load aesni-intel module like modprobe aesni-intel ?
Loading this module makes no difference in openssl speed output.
openssl speed -elapsed -evp aes-128-cbc
before loading aesni-intel module
type 16 bytes 64 bytes256 bytes 1024 bytes 8192
bytes
aes-128-
Is there a mailing list that I can ask Rijndael-specific questions?
On Sat, Mar 16, 2013 at 3:25 AM, Ewen Chan wrote:
> Interesting...
>
> Does this necessarily implicitly implies that the Rijndael cipher was
> selected as the AES "winner" because it was also "simple" enough to be
> fast, while m
Interesting...
Does this necessarily implicitly implies that the Rijndael cipher was
selected as the AES "winner" because it was also "simple" enough to be
fast, while meeting the security and protection requirements when they
initiated the open call for proposals?
I didn't realize that the AES a
On Sat, Mar 16, 2013 at 01:16:23AM -0400, Ewen Chan wrote:
> Okay then, here's another one of my infamous dumb questions.
>
> If that's the case, then why do we need the AES-NI instruction set?
It's far from the first accelerated instruction set of dubious utility. ;)
Marketing... etc.
Actually
Okay then, here's another one of my infamous dumb questions.
If that's the case, then why do we need the AES-NI instruction set?
If it's likely going to be storage and/or network bandwidth limited;
wouldn't the improvements made by introducing and incorporating the
AES-NI instruction set be kind
On Sat, Mar 16, 2013 at 12:06:07AM -0400, Ewen Chan wrote:
> That's MUCH faster than I expect it to be (even with AES-NI) and the
> 888 MB/s is faster than any available storage host-bus interface we've
> got right now; so I want to make sure that I am not losing my marbles
> here in trying to make
Do these number make sense or seem reasonable?
(I'm running a Core i7 3930K that's been OC'd to 4.5 GHz up from the
stock 3.2 GHz, running cygwin 1.7.17 on Windows 7 x64 Professional,
with 64 GB of DDR3-1600)
~$ OPENSSL_ia32cap="~0x202" openssl speed -elapsed -evp aes-256-cbc
You have
a...okay. Gotcha.
Thanks!
On Fri, Mar 15, 2013 at 5:23 AM, Erwann Abalea
wrote:
> On a PC under Linux, you can do a "cat /proc/cpuinfo" and look for "aes" in
> the "flags".
> On a PC under any OS, get the CPUID, and look for bit 25 of ECX.
> That's not OpenSSL-related.
>
>
> The use of OPENS
On a PC under Linux, you can do a "cat /proc/cpuinfo" and look for "aes"
in the "flags".
On a PC under any OS, get the CPUID, and look for bit 25 of ECX.
That's not OpenSSL-related.
The use of OPENSSL_ia32cap environment variable allows you to alter the
CPUID result (only inside OpenSSL), and
