From: grumpy@mailfence.com
To: dm-crypt@saout.de
Subject: [dm-crypt] hardware accelerated encryption
Date: Mon, 18 Jan 2021 19:37:39 -0600 (CST) [thread overview]
Message-ID: <nycvar.QRO.7.76.2101181933360.17129@tehzcl5.tehzcl-arg> (raw)
i have two devices
odroid xu4 and odroid hc4
the xu4
root@odroid2:~# cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 420102 iterations per second for 256-bit key
PBKDF2-sha256 592415 iterations per second for 256-bit key
PBKDF2-sha512 317750 iterations per second for 256-bit key
PBKDF2-ripemd160 305885 iterations per second for 256-bit key
PBKDF2-whirlpool 62653 iterations per second for 256-bit key
argon2i 4 iterations, 123140 memory, 4 parallel threads (CPUs) for
256-bit key (requested 2000 ms time)
argon2id 4 iterations, 127349 memory, 4 parallel threads (CPUs) for
256-bit key (requested 2000 ms time)
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 61.4 MiB/s 98.6 MiB/s
serpent-cbc 128b 42.0 MiB/s 39.7 MiB/s
twofish-cbc 128b 59.8 MiB/s 57.6 MiB/s
aes-cbc 256b 47.6 MiB/s 74.1 MiB/s
serpent-cbc 256b 41.7 MiB/s 39.9 MiB/s
twofish-cbc 256b 59.5 MiB/s 57.5 MiB/s
aes-xts 256b 112.1 MiB/s 96.0 MiB/s
serpent-xts 256b 42.3 MiB/s 41.9 MiB/s
twofish-xts 256b 60.4 MiB/s 61.6 MiB/s
aes-xts 512b 86.6 MiB/s 72.6 MiB/s
serpent-xts 512b 42.7 MiB/s 42.1 MiB/s
twofish-xts 512b 60.8 MiB/s 61.4 MiB/s
the hc4
root@hc4:~# cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 407055 iterations per second for 256-bit key
PBKDF2-sha256 748982 iterations per second for 256-bit key
PBKDF2-sha512 385505 iterations per second for 256-bit key
PBKDF2-ripemd160 260063 iterations per second for 256-bit key
PBKDF2-whirlpool 97523 iterations per second for 256-bit key
argon2i 4 iterations, 454309 memory, 4 parallel threads (CPUs) for
256-bit key (requested 2000 ms time)
argon2id 4 iterations, 463593 memory, 4 parallel threads (CPUs) for
256-bit key (requested 2000 ms time)
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 513.5 MiB/s 660.6 MiB/s
serpent-cbc 128b 38.1 MiB/s 39.2 MiB/s
twofish-cbc 128b 49.1 MiB/s 51.0 MiB/s
aes-cbc 256b 438.5 MiB/s 598.5 MiB/s
serpent-cbc 256b 38.1 MiB/s 39.2 MiB/s
twofish-cbc 256b 49.1 MiB/s 51.0 MiB/s
aes-xts 256b 582.6 MiB/s 582.6 MiB/s
serpent-xts 256b 39.3 MiB/s 39.6 MiB/s
twofish-xts 256b 51.1 MiB/s 51.6 MiB/s
aes-xts 512b 533.8 MiB/s 533.9 MiB/s
serpent-xts 512b 39.3 MiB/s 39.6 MiB/s
twofish-xts 512b 51.1 MiB/s 51.6 MiB/s
how should i interpret this
_______________________________________________
dm-crypt mailing list
dm-crypt@saout.de
https://www.saout.de/mailman/listinfo/dm-crypt
reply other threads:[~2021-01-22 0:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.2101181933360.17129@tehzcl5.tehzcl-arg \
--to=grumpy@mailfence.com \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).