[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53F4E571.7030003@gmail.com>
Date: Wed, 20 Aug 2014 20:14:09 +0200
From: Milan Broz <gmazyland@...il.com>
To: Jussi Kivilinna <jussi.kivilinna@....fi>
CC: Stephan Mueller <smueller@...onox.de>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: Kernel crypto API: cryptoperf performance measurement
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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists