Am Donnerstag, 26. Mai 2016, 19:30:01 schrieb Stephan Mueller:
Hi,
>
> However, the key difference to a standard speed test is that I set up a new
> key schedule quite frequently. And I would suspect that something is going
> on here...
With tcrypt, there is some interesting hint: on smaller blocks, the C
implementation is indeed faster:
[ 20.391510]
testing speed of async ecb(aes) (ecb(aes-generic)) encryption
20.391513] test 0 (128 bit key, 16 byte blocks): 1 operation in 275 cycles
(16 bytes)
[ 20.391517] test 1 (128 bit key, 64 byte blocks): 1 operation in 702 cycles
(64 bytes)
[ 20.391521] test 2 (128 bit key, 256 byte blocks): 1 operation in 2431
cycles (256 bytes)
[ 20.391532] test 3 (128 bit key, 1024 byte blocks): 1 operation in 9347
cycles (1024 bytes)
[ 20.391570] test 4 (128 bit key, 8192 byte blocks): 1 operation in 74375
cycles (8192 bytes)
vs for ecb-aes-aesni:
[ 143.482123] test 0 (128 bit key, 16 byte blocks): 1 operation in 1203
cycles (16 bytes)
[ 143.482138] test 1 (128 bit key, 64 byte blocks): 1 operation in 1328
cycles (64 bytes)
[ 143.482148] test 2 (128 bit key, 256 byte blocks): 1 operation in 1922
cycles (256 bytes)
[ 143.482159] test 3 (128 bit key, 1024 byte blocks): 1 operation in 3328
cycles (1024 bytes)
[ 143.482176] test 4 (128 bit key, 8192 byte blocks): 1 operation in 19483
cycles (8192 bytes)
As I use crypto_cipher_encrypt_one, I only send one block at a time to AES-NI.
Ciao
Stephan
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
