public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Michal Ludvig <michal@logix.cz>
Cc: James Morris <jmorris@redhat.com>, Andrew Morton <akpm@osdl.org>,
	"David S. Miller" <davem@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Support for VIA PadLock crypto engine
Date: Thu, 13 May 2004 15:59:04 +0300	[thread overview]
Message-ID: <40A37118.ED58E781@users.sourceforge.net> (raw)
In-Reply-To: Pine.LNX.4.53.0405121546200.24118@maxipes.logix.cz

Michal Ludvig wrote:
> My padlock driver can be used for anything that uses CryptoAPI and in fact
> it speeds things a lot (see a simple disk-based benchmark at
> http://www.logix.cz/michal/dl/padlock.xp).

Cryptoapi version of AES is slowest implementation of AES that I know of.
For speed tests, please compare against more modern implementation.

Below is one old AES128 speed test that I ran on my 300 MHz test box:

KERNEL      IMPLEMENTATION  MODE                WRITE MiB/s     READ MiB/s
2.6.1       cryptoloop      single-key           5.21            4.08
2.6.1       loop-AES        single-key           9.52            7.56
2.6.1       loop-AES        multi-key(MD5 IV)    7.67            6.35
2.4.22aa1   loop-AES        single-key          10.55           10.16
2.4.22aa1   loop-AES        multi-key(MD5 IV)    8.75            8.13

The cryptoloop implementation is busted in more than one way, so it is
useless for security needs:

http://marc.theaimsgroup.com/?l=linux-kernel&m=107419912024246&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=107719798631935&w=2

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD

  parent reply	other threads:[~2004-05-13 12:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-10 14:40 [PATCH 2/2] Support for VIA PadLock crypto engine Michal Ludvig
2004-05-10 15:55 ` James Morris
2004-05-10 19:23   ` Michal Ludvig
2004-05-11 16:56   ` [PATCH 1/2] " Michal Ludvig
2004-05-12  8:55     ` Michal Ludvig
2004-05-11 16:56   ` [PATCH 2/2] " Michal Ludvig
2004-05-12 13:37     ` James Morris
2004-05-12 14:42       ` Michal Ludvig
2004-05-12 14:52         ` James Morris
2004-05-12 15:25           ` Michal Ludvig
2004-05-13  0:44             ` James Morris
2004-05-14 15:10               ` New list for CryptoAPI development Michal Ludvig
2004-05-17  8:39                 ` Arnd Bergmann
2004-05-17  8:53                   ` Michal Ludvig
2004-05-13 12:59         ` Jari Ruusu [this message]
2004-05-13 18:30           ` [PATCH 2/2] Support for VIA PadLock crypto engine Andrew Morton
2004-05-13 19:02             ` Jari Ruusu
2004-05-13 20:00               ` Michal Ludvig
2004-05-14 13:31                 ` Jari Ruusu
2004-05-14 14:09                   ` Fruhwirth Clemens
2004-05-14 16:05                     ` Jari Ruusu
2004-05-16 15:32                       ` Fruhwirth Clemens
2004-05-16 17:46                         ` Jari Ruusu
2004-05-11 17:04   ` [PATCH 3/2 :-] " Michal Ludvig

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=40A37118.ED58E781@users.sourceforge.net \
    --to=jariruusu@users.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=davem@redhat.com \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal@logix.cz \
    /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