public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
To: cryptodev-linux-devel@gna.org,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: comparison of the AF_ALG interface with the /dev/crypto
Date: Sun, 28 Aug 2011 15:17:00 +0200	[thread overview]
Message-ID: <4E5A3FCC.2030504@gnutls.org> (raw)

Hello,
  I've compared the cryptodev [0] and AF_ALG interfaces in terms of
performance [1]. I've put the results, as well as the benchmarks used
in: http://home.gna.org/cryptodev-linux/comparison.html

The benchmark idea was to test the speed of initialization, encryption
and deinitiation, as well as the encryption speed alone. These are the
most common use cases of the frameworks (i.e. how they would be used by 
a cryptographic library).

The AF_ALG appears to have poor performance comparing to cryptodev. Note
that the test with software AES is not really indicative because the
cost of software encryption masks the overhead of the framework. The
difference is clearly seen in the NULL cipher that has no cost (as one
would expect from a hardware cipher accelerator).

Given my benchmarks have no issues, it is not apparent to me why one
should use AF_ALG instead of cryptodev. I do not know though why AF_ALG
performs so poor. I'd speculate by blaming it on the usage of the socket
API and the number of system calls required.

regards,
Nikos

[0]. http://home.gna.org/cryptodev-linux/
[1]. Both intend to provide user-space with high-bandwidth hardware 
accelerated ciphers, thus performance seems a rational to compare.

             reply	other threads:[~2011-08-28 13:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-28 13:17 Nikos Mavrogiannopoulos [this message]
2011-08-28 20:35 ` comparison of the AF_ALG interface with the /dev/crypto 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
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=4E5A3FCC.2030504@gnutls.org \
    --to=nmav@gnutls.org \
    --cc=cryptodev-linux-devel@gna.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox