From: Stephan Mueller <smueller@chronox.de>
To: noloader@gmail.com
Cc: linux-crypto@vger.kernel.org
Subject: Re: AES-NI: slower than aes-generic?
Date: Thu, 26 May 2016 19:30:01 +0200 [thread overview]
Message-ID: <3163610.mmC4VCYNt8@tauon.atsec.com> (raw)
In-Reply-To: <CAH8yC8mibb90J2rkD_YzM2X1HsNuHEOLbV7Wntq39dMxH4KCnQ@mail.gmail.com>
Am Donnerstag, 26. Mai 2016, 13:25:02 schrieb Jeffrey Walton:
Hi Jeffrey,
> > What I am wondering is that when encrypting 256 16 byte blocks, I get a
> > speed of about 170 MB/s with the AES-NI driver. When using the
> > aes-generic or aes- asm, I get up to 180 MB/s with all else being equal.
> > Note, that figure includes a copy_to_user of the generated data.
> >
> > ...
>
> Something sounds amiss.
>
> AES-NI should be on the order of magnitude faster than a generic
> implementation. Can you verify AES-NI is actually using AES-NI, and
> aes-generic is a software implementation?
I am pretty sure I am using the right implementations as I checked the
refcount in /proc/crypto.
>
> Here are some OpenSSL numbers. EVP uses AES-NI when available.
> Omitting -evp means its software only (no hardware acceleration, like
> AES-NI).
I understand that AES-NI should be faster. That is what I am wondering about.
However, the key difference to a standard speed test is that I set up a new
key schedule quite frequently. And I would suspect that something is going on
here...
Ciao
Stephan
next prev parent reply other threads:[~2016-05-26 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 16:10 AES-NI: slower than aes-generic? Stephan Mueller
2016-05-26 17:25 ` Jeffrey Walton
2016-05-26 17:30 ` Stephan Mueller [this message]
2016-05-26 18:14 ` Stephan Mueller
2016-05-26 18:20 ` Sandy Harris
2016-05-26 18:49 ` Stephan Mueller
2016-05-26 19:15 ` Sandy Harris
2016-05-27 2:14 ` Theodore Ts'o
2016-05-27 7:08 ` Stephan Mueller
2016-05-27 20:40 ` Jeffrey Walton
2016-06-08 12:21 ` Stephan Mueller
2016-05-28 0:28 ` Aaron Zauner
2016-05-29 19:51 ` Stephan Mueller
2016-05-30 4:08 ` Theodore Ts'o
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=3163610.mmC4VCYNt8@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=linux-crypto@vger.kernel.org \
--cc=noloader@gmail.com \
/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.