From: Stephan Mueller <smueller@chronox.de>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Subject: Kernel crypto API: cryptoperf performance measurement
Date: Sun, 17 Aug 2014 17:55:51 +0200 [thread overview]
Message-ID: <56334718.JSiBY74glM@myon.chronox.de> (raw)
Hi,
during playing around with the kernel crypto API, I implemented a performance
measurement tool kit for the various kernel crypto API cipher types. The
cryptoperf tool kit is provided in [1].
Comments are welcome.
In general, the results are as expected, i.e. the assembler implementations
are faster than the pure C implementations. However, there are curious results
which probably should be checked by the maintainers of the respective ciphers
(hoping that my tool works correctly ;-) ):
ablkcipher
----------
- cryptd is slower by factor 10 across the board
blkcipher
---------
- Blowfish x86_64 assembler together with the generic C block chaining modes
is significantly slower than Blowfish implemented in generic C
- Blowfish x86_64 assembler in ECB is significantly slower than generic C
Blowfish ECB
- Serpent assembler implementations are not significantly faster than generic
C implementations
- AES-NI ECB, LRW, CTR is significantly slower than AES i586 assembler.
- AES-NI ECB, LRW, CTR is not significantly faster than AES generic C
rng
---
- The ANSI X9.31 RNG seems to work massively faster than the underlying AES
cipher (by about a factor of 5). I am unsure about the cause of this.
Caveat
------
Please note that there is one small error which I am unsure how to fix it as
documented in the TODO file.
[1] http://www.chronox.de/cryptoperf.html
--
Ciao
Stephan
next reply other threads:[~2014-08-17 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 15:55 Stephan Mueller [this message]
2014-08-19 7:17 ` Kernel crypto API: cryptoperf performance measurement Jussi Kivilinna
2014-08-19 18:23 ` Stephan Mueller
2014-08-20 13:25 ` Jussi Kivilinna
2014-08-20 18:14 ` Milan Broz
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=56334718.JSiBY74glM@myon.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.