[dm-crypt] REQUIRED CIPHERS TEST takes 20 minutes each for aes-related ciphers

christian at madez.de christian at madez.de
Thu Nov 28 15:54:20 CET 2013


El 2013-11-28 14:30, shmick at riseup.net escribió:
> christian at madez.de:
>> Hello,
>>
>> I just compiled cryptsetup-1.6.2 on a machine with AES-NI. During 
>> the
>> compilation there were some tests. The lines of the output when the
>> issue occurred were:
>>
>> REQUIRED CIPHERS TEST
>> #  Algorithm | Key |  Encryption |  Decryption
>>      aes-cbc   256b   975.0 MiB/s  2037065.0 MiB/s
>>      aes-lrw   384b  103909.0 MiB/s  158691.0 MiB/s
>>      aes-xts   512b  1731833.0 MiB/s  1681613.0 MiB/s
>>  twofish-cbc   256b   241.3 MiB/s   499.5 MiB/s
>>  twofish-lrw   384b   448.6 MiB/s   453.0 MiB/s
>>  twofish-xts   512b   497.0 MiB/s   496.0 MiB/s
>>  serpent-cbc   256b   108.5 MiB/s   351.3 MiB/s
>>  serpent-lrw   384b   333.7 MiB/s   333.0 MiB/s
>>  serpent-xts   512b   363.3 MiB/s   341.0 MiB/s
>> blowfish-cbc   256b   129.6 MiB/s   500.5 MiB/s
>> des3_ede-cbc   192b    34.3 MiB/s    35.4 MiB/s
>>    cast5-cbc   128b   121.9 MiB/s   474.0 MiB/s
>
> when these tests ran did all cores process or just 1 single core ?

For aes-cbc, aes-lrw and aes-xts just one core was used (and maxed 
out).
However, it took orders of magnitudes longer.

> do you know if cryptsetup can take advantage of multi threading on 
> multi
> core processors ?

No.

>>
>> The tests for aes-cbc, aes-lrw and aes-xts took very long (nearly 
>> one
>> hour for all three combined) on a Intel Core i5-4670K. All other 
>> tests
>> were finished in a few seconds.
>>
>> Is this wanted behavior?
>>
>> Best regards,
>> Christian Weinz
>> _______________________________________________
>> dm-crypt mailing list
>> dm-crypt at saout.de
>> http://www.saout.de/mailman/listinfo/dm-crypt
>>



More information about the dm-crypt mailing list