Michael wrote: > On Friday, 13 October 2023 02:35:21 BST Dale wrote: > >> root@fireball / # cryptsetup benchmark >> # Tests are approximate using memory only (no storage IO). >> PBKDF2-sha1 878204 iterations per second for 256-bit key >> PBKDF2-sha256 911805 iterations per second for 256-bit key >> PBKDF2-sha512 698119 iterations per second for 256-bit key >> PBKDF2-ripemd160 548418 iterations per second for 256-bit key >> PBKDF2-whirlpool 299251 iterations per second for 256-bit key >> argon2i 4 iterations, 1048576 memory, 4 parallel threads (CPUs) >> for 256-bit key (requested 2000 ms time) >> argon2id 4 iterations, 1048576 memory, 4 parallel threads (CPUs) >> for 256-bit key (requested 2000 ms time) >> # Algorithm | Key | Encryption | Decryption >> aes-cbc 128b 63.8 MiB/s 51.4 MiB/s >> serpent-cbc 128b 90.9 MiB/s 307.6 MiB/s >> twofish-cbc 128b 200.4 MiB/s 218.4 MiB/s >> aes-cbc 256b 54.6 MiB/s 37.5 MiB/s >> serpent-cbc 256b 90.4 MiB/s 302.6 MiB/s >> twofish-cbc 256b 198.2 MiB/s 216.7 MiB/s >> aes-xts 256b 68.0 MiB/s 45.0 MiB/s >> serpent-xts 256b 231.9 MiB/s 227.6 MiB/s >> twofish-xts 256b 191.8 MiB/s 163.1 MiB/s >> aes-xts 512b 42.4 MiB/s 18.9 MiB/s >> serpent-xts 512b 100.9 MiB/s 124.6 MiB/s >> twofish-xts 512b 154.8 MiB/s 173.3 MiB/s >> root@fireball / # >> >> >> >> root@nas:~# cryptsetup benchmark >> # Tests are approximate using memory only (no storage IO). >> PBKDF2-sha1 741567 iterations per second for 256-bit key >> PBKDF2-sha256 910222 iterations per second for 256-bit key >> PBKDF2-sha512 781353 iterations per second for 256-bit key >> PBKDF2-ripemd160 547845 iterations per second for 256-bit key >> PBKDF2-whirlpool 350929 iterations per second for 256-bit key >> argon2i 4 iterations, 571787 memory, 4 parallel threads (CPUs) for >> 256-bit key (requested 2000 ms time) >> argon2id 4 iterations, 524288 memory, 4 parallel threads (CPUs) for >> 256-bit key (requested 2000 ms time) >> # Algorithm | Key | Encryption | Decryption >> aes-cbc 128b 130.6 MiB/s 128.0 MiB/s >> serpent-cbc 128b 64.7 MiB/s 161.8 MiB/s >> twofish-cbc 128b 175.4 MiB/s 218.8 MiB/s >> aes-cbc 256b 120.1 MiB/s 122.2 MiB/s >> serpent-cbc 256b 84.5 MiB/s 210.8 MiB/s >> twofish-cbc 256b 189.5 MiB/s 218.6 MiB/s >> aes-xts 256b 167.0 MiB/s 162.1 MiB/s >> serpent-xts 256b 173.9 MiB/s 204.5 MiB/s >> twofish-xts 256b 204.4 MiB/s 213.2 MiB/s >> aes-xts 512b 127.9 MiB/s 122.9 MiB/s >> serpent-xts 512b 201.5 MiB/s 204.7 MiB/s >> twofish-xts 512b 215.0 MiB/s 213.0 MiB/s >> root@nas:~# >> >> >> >> Is that about what you would expect? Fireball is on a 970 mobo. It's >> slightly newer. I think the 770T is about 2 years older, maybe 3. > grep AES /usr/src/linux/.config > > or, > > zgrep AES /proc/config.gz > > Or, grep your *current* kernel config wherever it is stored.
I got the idea but assuming you wanted that info from the NAS box, I had to dig a little. It's Ubuntu. It doesn't have kernel sources, no config.gz in /proc either. I found this. I assume it is accurate. Hopefully. root@nas:~# cat /boot/config-5.15.0-86-generic | grep -i aes CONFIG_SND_MAESTRO3=m CONFIG_SND_MAESTRO3_INPUT=y CONFIG_CRYPTO_AEGIS128_AESNI_SSE2=m CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_AES_TI=m CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=m CONFIG_CRYPTO_SM4_AESNI_AVX_X86_64=m CONFIG_CRYPTO_SM4_AESNI_AVX2_X86_64=m CONFIG_CRYPTO_DEV_PADLOCK_AES=m CONFIG_CRYPTO_LIB_AES=y root@nas:~# I don't usually use modules. So, this is not something I run into much. I'm adding this info since I think it will help as well. root@nas:~# lsmod | grep -i aes root@nas:~# I see the main aes option is built in so it shouldn't be listed above if I recall correctly. The other two options are modules but not loaded. That said, I don't know if they are needed either. On my main rig, I have AES_TI built in. Anyway, I thought I would include that in case it helps. I was thinking about later on upgrading the CPU to a 6 core version. I may research and see if it includes the aes instruction set. It may help. It may not. Right now, I don't know if the 770T is even going to be a NAS box and need encryption. It could be that given that mobo and CPUs age, it's doing the best it can. After all, the Dell box was also fairly slow. Dale :-) :-)
