From: Milan Broz <gmazyland@gmail.com>
To: Jussi Kivilinna <jussi.kivilinna@iki.fi>
Cc: Stephan Mueller <smueller@chronox.de>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: Kernel crypto API: cryptoperf performance measurement
Date: Wed, 20 Aug 2014 20:14:09 +0200 [thread overview]
Message-ID: <53F4E571.7030003@gmail.com> (raw)
In-Reply-To: <53F4A1E7.8090504@iki.fi>
On 08/20/2014 03:25 PM, Jussi Kivilinna wrote:
>> One to four GB per second for XTS? 12 GB per second for AES CBC? Somehow that
>> does not sound right.
>
> Agreed, those do not look correct... I wonder what happened there. On
> new run, I got more sane results:
Which cryptsetup version are you using?
There was a bug in that test on fast machines (fixed in 1.6.3, I hope :)
But anyway, it is not intended as rigorous speed test,
it was intended for comparison of ciphers speed on particular machine.
Test basically tries to encrypt 1MB block (or multiple of this
if machine is too fast). All it runs through kernel userspace crypto API
interface.
(Real FDE is always slower because it runs over 512bytes blocks.)
Milan
>
> # Algorithm | Key | Encryption | Decryption
> aes-cbc 128b 139,1 MiB/s 1713,6 MiB/s
> serpent-cbc 128b 62,2 MiB/s 232,9 MiB/s
> twofish-cbc 128b 116,3 MiB/s 243,7 MiB/s
> aes-cbc 256b 375,1 MiB/s 1159,4 MiB/s
> serpent-cbc 256b 62,1 MiB/s 214,9 MiB/s
> twofish-cbc 256b 139,3 MiB/s 217,5 MiB/s
> aes-xts 256b 1296,4 MiB/s 1272,5 MiB/s
> serpent-xts 256b 283,3 MiB/s 275,6 MiB/s
> twofish-xts 256b 294,8 MiB/s 299,3 MiB/s
> aes-xts 512b 984,3 MiB/s 991,1 MiB/s
> serpent-xts 512b 227,7 MiB/s 220,6 MiB/s
> twofish-xts 512b 220,6 MiB/s 220,2 MiB/s
>
> -Jussi
>
next prev parent reply other threads:[~2014-08-20 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 15:55 Kernel crypto API: cryptoperf performance measurement Stephan Mueller
2014-08-19 7:17 ` Jussi Kivilinna
2014-08-19 18:23 ` Stephan Mueller
2014-08-20 13:25 ` Jussi Kivilinna
2014-08-20 18:14 ` Milan Broz [this message]
2014-08-21 7:38 ` Jussi Kivilinna
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=53F4E571.7030003@gmail.com \
--to=gmazyland@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jussi.kivilinna@iki.fi \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.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 NNTP newsgroup(s).