From: Peter Wu <peter@lekensteyn.nl>
To: linux-crypto@vger.kernel.org
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Andreas Steinmetz <ast@domdv.de>
Subject: aes-x86_64 seems slower than the generic implementation
Date: Sat, 19 Apr 2014 16:42:07 +0200 [thread overview]
Message-ID: <2046035.alMyLlD0ki@al> (raw)
Hi!
When comparing the x86_64 assembly implementation (module aes-x86_64) against
the generic AES implementation, I found that the generic implementation was
consistenly faster.
Test setup #1:
* cryptsetup 1.6.4
* Linux v3.15-rc1-356-gebfc45e,
https://github.com/Lekensteyn/aur/blob/1d1950/linux-custom/config
* CPU: Intel i5-460M
* Distro: Arch Linux x86_64
Command:
for i in {0..10};do cryptsetup benchmark --cipher aes-xts; done
Test results for n=11, mean (+ standard deviation), enc/dec:
* aes-x86_64: 139.6 (0.68) / 138.5 (0.22)
* aes-generic: 144.8 (0.63) / 144.6 (0.31)
About a month ago, I conducted a similar test on a different machine[1].
* cryptsetup 1.6.4
* QEMU: 1.7.0
* Linux (guest, no modules): v3.14-rc7-59-g08edb33
* Linux (host): v3.14-rc5
* CPU: Intel i7-3770
Test results comparing aes-generic, aes-x86_64 and AESNI (n=3):
generic x86_64 aesni
* aes-cbc-128 201/276 200/280 669/2500
* aes-cbc-256 162/205 159/208 492/1835
* aes-xts-256 275/270 272/276 2050/2034
(note, AES-NI performance varies a lot)
Aren't the assembly implementations supposed to be faster?
Kind regards,
Peter
[1]: https://lekensteyn.nl/files/linux-crypto-benchmark/
reply other threads:[~2014-04-19 14:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2046035.alMyLlD0ki@al \
--to=peter@lekensteyn.nl \
--cc=ast@domdv.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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 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.