From: Phil Sutter <phil@nwl.cc>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: nmav@gnutls.org, cryptodev-linux-devel@gna.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: comparison of the AF_ALG interface with the /dev/crypto
Date: Thu, 1 Sep 2011 17:09:28 +0200 [thread overview]
Message-ID: <20110901150928.GC14522@orbit.nwl.cc> (raw)
In-Reply-To: <20110901141445.GA31447@gondor.apana.org.au>
Herbert,
On Thu, Sep 01, 2011 at 10:14:45PM +0800, Herbert Xu wrote:
> Phil Sutter <phil@nwl.cc> wrote:
> >
> > chunksize af_alg cryptodev (100 * cryptodev / af_alg)
> > --------------------------------------------------------------------------
> > 512 4.169 MB/s 7.113 MB/s 171 %
> > 1024 7.904 MB/s 12.957 MB/s 164 %
> > 2048 13.163 MB/s 19.683 MB/s 150 %
> > 4096 20.218 MB/s 26.960 MB/s 133 %
> > 8192 27.539 MB/s 34.373 MB/s 125 %
> > 16384 33.730 MB/s 39.997 MB/s 119 %
> > 32768 37.399 MB/s 42.727 MB/s 114 %
> > 65536 40.004 MB/s 44.660 MB/s 112 %
>
> Are you maxing out your submission CPU? If not then you're testing
> the latency of the interface, as opposed to the throughput.
Good point. So in order to also test the throughput, I've put my OpenRD
under load:
| stress -c 2 -i 2 -m 2 --vm-bytes 64MB
and ran the tests again:
chunksize af_alg cryptodev (100 * cryptodev / af_alg)
--------------------------------------------------------------------------
512 0.618 MB/s 1.14 MB/s 184 %
1024 1.258 MB/s 2.28 MB/s 181 %
2048 2.453 MB/s 4.39 MB/s 179 %
4096 4.540 MB/s 7.76 MB/s 171 %
8192 7.981 MB/s 11.67 MB/s 146 %
16384 12.543 MB/s 14.08 MB/s 112 %
32768 13.139 MB/s 14.46 MB/s 110 %
65536 14.254 MB/s 15.55 MB/s 109 %
So that means cryptodev-linux is superior in throughput as well as
latency, right? Or is it the lower latency of the interface causing the
higher throughput?
Greetings, Phil
next prev parent reply other threads:[~2011-09-01 15:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-28 13:17 comparison of the AF_ALG interface with the /dev/crypto Nikos Mavrogiannopoulos
2011-08-28 20:35 ` David Miller
2011-08-29 7:32 ` Nikos Mavrogiannopoulos
2011-08-29 16:09 ` David Miller
2011-08-30 16:33 ` [Cryptodev-linux-devel] " Phil Sutter
2011-09-01 2:15 ` Herbert Xu
2011-09-01 6:26 ` Nikos Mavrogiannopoulos
2011-09-01 6:43 ` Herbert Xu
2011-09-01 6:54 ` Nikos Mavrogiannopoulos
2011-09-01 6:56 ` Herbert Xu
2011-09-01 13:39 ` Phil Sutter
2011-09-01 14:14 ` Herbert Xu
2011-09-01 14:56 ` Nikos Mavrogiannopoulos
2011-09-01 14:59 ` Herbert Xu
2011-09-01 15:06 ` Nikos Mavrogiannopoulos
2011-09-01 15:08 ` Herbert Xu
2011-09-01 15:32 ` David Miller
2011-09-01 16:19 ` Nikos Mavrogiannopoulos
2011-09-01 15:09 ` Phil Sutter [this message]
2011-09-01 15:13 ` Herbert Xu
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=20110901150928.GC14522@orbit.nwl.cc \
--to=phil@nwl.cc \
--cc=cryptodev-linux-devel@gna.org \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmav@gnutls.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox