From: Matthias Schniedermeyer <ms@citd.de>
To: "shmick@riseup.net" <shmick@riseup.net>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] benchmark, kernel, libgcrypt, comparisons
Date: Thu, 30 Jan 2014 23:10:21 +0100 [thread overview]
Message-ID: <20140130221021.GA8079@citd.de> (raw)
In-Reply-To: <52E90EA3.2020404@riseup.net>
On 30.01.2014 01:22, shmick@riseup.net wrote:
> serpent decryption is vastly faster, twofish in general but seems AES isn't
>
> # Algorithm | Key | Encryption | Decryption
> aes-cbc 128b 150.2 MiB/s 180.4 MiB/s
> aes-cbc 256b 117.5 MiB/s 136.0 MiB/s
> aes-xts 256b 171.3 MiB/s 176.6 MiB/s
> aes-xts 512b 131.4 MiB/s 134.1 MiB/s
Just to get a little indication of the "smidge" better performance of
hardware accelerated AES.
This is what i get for AES on Core i7 4770 (a.k.a. Haswell)
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 753.2 MiB/s 3305.0 MiB/s
aes-cbc 256b 551.4 MiB/s 2509.0 MiB/s
aes-xts 256b 2799.0 MiB/s 2853.0 MiB/s
aes-xts 512b 2154.0 MiB/s 2162.0 MiB/s
--
Matthias
prev parent reply other threads:[~2014-01-30 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 14:22 [dm-crypt] benchmark, kernel, libgcrypt, comparisons shmick
2014-01-29 14:59 ` Milan Broz
2014-01-29 15:52 ` shmick
2014-01-30 22:10 ` Matthias Schniedermeyer [this message]
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=20140130221021.GA8079@citd.de \
--to=ms@citd.de \
--cc=dm-crypt@saout.de \
--cc=shmick@riseup.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.