From: James Morris <jmorris@intercode.com.au>
To: Jari Ruusu <jari.ruusu@pp.inet.fi>
Cc: Christoph Hellwig <hch@infradead.org>,
Chris Friesen <cfriesen@nortelnetworks.com>,
Andrew Morton <akpm@osdl.org>, <Andries.Brouwer@cwi.nl>,
<akpm@digeo.com>, <linux-kernel@vger.kernel.org>,
<torvalds@osdl.org>
Subject: Re: [PATCH] cryptoloop
Date: Sun, 6 Jul 2003 03:16:09 +1000 (EST) [thread overview]
Message-ID: <Mutt.LNX.4.44.0307060312520.21967-100000@excalibur.intercode.com.au> (raw)
In-Reply-To: <3F068F49.1883BE0D@pp.inet.fi>
On Sat, 5 Jul 2003, Jari Ruusu wrote:
> This tests only low level cipher functions aes_encrypt() and aes_decrypt()
> from linux-2.5.74/crypto/aes.c with all CryptoAPI overhead removed. In real
> use, including CryptoAPI overhead, these numbers should be a little bit
> smaller.
>
> key length 128 bits, encrypt speed 68.5 Mbits/sec
> key length 128 bits, decrypt speed 58.9 Mbits/sec
> key length 192 bits, encrypt speed 58.3 Mbits/sec
> key length 192 bits, decrypt speed 50.3 Mbits/sec
> key length 256 bits, encrypt speed 51.0 Mbits/sec
> key length 256 bits, decrypt speed 43.8 Mbits/sec
[snip]
> This tests aes_encrypt() and aes_decrypt() from loop-AES-v1.7d/aes.c
> Loop-AES users running non-x86 kernels or x86 configured for i386/i486 will
> run this version.
>
> key length 128 bits, encrypt speed 81.2 Mbits/sec
> key length 128 bits, decrypt speed 83.4 Mbits/sec
> key length 192 bits, encrypt speed 68.5 Mbits/sec
> key length 192 bits, decrypt speed 70.6 Mbits/sec
> key length 256 bits, encrypt speed 58.9 Mbits/sec
> key length 256 bits, decrypt speed 60.9 Mbits/sec
These results are interesting, if they represent a pure comparison of the
crypto algorithm implementations -- both the mainline kernel version and
yours are based on the same Gladman code.
- James
--
James Morris
<jmorris@intercode.com.au>
next prev parent reply other threads:[~2003-07-05 17:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 18:44 Andries.Brouwer
2003-07-02 19:02 ` Andrew Morton
2003-07-02 19:16 ` Linus Torvalds
2003-07-02 19:20 ` Andrew Morton
2003-07-02 19:31 ` Linus Torvalds
2003-07-03 11:21 ` Jari Ruusu
2003-07-03 15:20 ` Andrew Morton
2003-07-03 17:29 ` Jari Ruusu
2003-07-03 17:38 ` Chris Friesen
2003-07-04 7:43 ` Jari Ruusu
2003-07-04 8:44 ` Andrew Morton
2003-07-04 9:41 ` Christoph Hellwig
2003-07-05 8:41 ` Jari Ruusu
2003-07-05 8:58 ` Andrew Morton
2003-07-05 9:00 ` Andre Hedrick
2003-07-05 9:10 ` Andre Hedrick
2003-07-05 17:16 ` James Morris [this message]
2003-07-05 17:20 ` Linus Torvalds
2003-07-08 12:43 ` Christoph Hellwig
2003-07-04 9:39 ` Christoph Hellwig
2003-07-03 16:20 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2003-07-04 13:21 Andries.Brouwer
2003-07-04 13:28 ` Christoph Hellwig
2003-07-04 11:08 Andries.Brouwer
2003-07-04 12:13 ` Christoph Hellwig
2003-07-03 16:25 Andries.Brouwer
2003-07-03 16:31 ` Christoph Hellwig
2003-07-02 22:57 Andries.Brouwer
2003-07-02 22:27 Andries.Brouwer
2003-07-02 21:00 Andries.Brouwer
2003-07-02 21:06 ` Greg KH
2003-07-02 21:31 ` Andrew Morton
2003-07-03 16:23 ` Christoph Hellwig
2003-07-02 19:42 Andries.Brouwer
2003-07-02 19:58 ` Andrew Morton
2003-07-02 15:21 Andries.Brouwer
2003-07-02 17:16 ` Andrew Morton
2003-07-03 15:44 ` Christoph Hellwig
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=Mutt.LNX.4.44.0307060312520.21967-100000@excalibur.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=akpm@osdl.org \
--cc=cfriesen@nortelnetworks.com \
--cc=hch@infradead.org \
--cc=jari.ruusu@pp.inet.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®