| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 21 Aug 2014 10:38:03 +0300 From: Jussi Kivilinna <jussi.kivilinna@....fi> To: Milan Broz <gmazyland@...il.com> 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 2014-08-20 21:14, Milan Broz wrote: > 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 :) I had version 1.6.1 at hand. > > But anyway, it is not intended as rigorous speed test, > it was intended for comparison of ciphers speed on particular machine. > True, but it's nice easy test when compared to parsing results from tcrypt speed tests. -Jussi > 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 > -- 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