All of lore.kernel.org
 help / color / mirror / Atom feed
From: David McCullough <david_mccullough@au.securecomputing.com>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ACRYPTO] New asynchronous crypto layer release.
Date: Wed, 24 May 2006 09:04:43 +1000	[thread overview]
Message-ID: <20060523230443.GG15545@beast> (raw)
In-Reply-To: <20060521131429.GA9789@2ka.mipt.ru>


Hi Evgeniy,

Just interested in the results you are getting below for
comparison to what I see under OCF with Openswan.

What sort of hifn card were you using in the test below,
was it a 7956 PCIX (ie., 64bit?)

How did you measure the throughput  ?

I can post the OCF numbers,  but it doesn't mean a lot
unless it's a fair comparison :-)

Cheers,
Davidm


Jivin Evgeniy Polyakov lays it down ...
> New asynchronous crypto layer acrypto [1] release.
> It includes new driver for HIFN 7955/7956 adapters,
> VIA padlock driver, driver for CE-InfoSys FastCrypt PCI card equipped
> with a SuperCrypt CE99C003B and
> dm-crypt and IPsec ESP4 engines ported to acrypto.
> 
> Psec ESP4 transport mode benchmark (scp):
>         2.6.16-1.2069_FC4smp -> vanilla 2.6.16-git: ~11.8 MB/s
> 	vanilla 2.6.16-git -> 2.6.16-1.2069_FC4smp: ~13.2 MB/s
> 
> 	2.6.16-1.2069_FC4smp -> acrypto SW 2.6.16: ~12.6 MB/s
> 	acrypto SW 2.6.16 -> 2.6.16-1.2069_FC4smp: ~13.5 MB/s
> 
> IPsec benchmark with HIFN driver:
> 	2.6.16-1.2069_FC4smp -> vanilla 2.6.16-git: ~11.8 MB/s
> 	vanilla 2.6.16-git -> 2.6.16-1.2069_FC4smp: ~13.2 MB/s
> 
> 	2.6.16-1.2069_FC4smp -> acrypto HIFN 2.6.16: ~13.2 MB/s
> 	acrypto HIFN 2.6.16 -> 2.6.16-1.2069_FC4smp: ~13.5 MB/s
> 
> As you might expect, CPU usage with HIFN driver and acrypto is noticebly
> less, since that setup is CPU limited for stock synchronous kernel
> setup (3Ghz P4 with HT enabled).
> Above numbers drift with the time, especially when machine running
> stock FC4 kernel overheats, and that numbers decrease to 12-13 MB/s.
> 
> One can find combined patchsets for 2.6.15 and 2.6.16 trees which
> include acrypto with SW crypto provider, dm-crypt and IPsec engines
> at acrypto homepage [1].
> 
> Credits.
> Yakov Lerner for great testing and bug-hunting.
> Michal Ludvig for original VIA padlock and fcrypt drivers.
> 
> 
> Thank you.
> 
> 1. Asynchronous crypto layer acrypto.
> http://tservice.net.ru/~s0mbre/old/?section=projects&item=acrypto
> 
> -- 
> 	Evgeniy Polyakov
> -
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
David McCullough,  david_mccullough@securecomputing.com,   Ph:+61 734352815
Secure Computing - SnapGear  http://www.uCdot.org http://www.cyberguard.com

  reply	other threads:[~2006-05-23 23:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21 13:14 [ACRYPTO] New asynchronous crypto layer release Evgeniy Polyakov
2006-05-23 23:04 ` David McCullough [this message]
2006-05-24  7:12   ` Evgeniy Polyakov
2006-05-25  0:03     ` David McCullough

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=20060523230443.GG15545@beast \
    --to=david_mccullough@au.securecomputing.com \
    --cc=johnpol@2ka.mipt.ru \
    --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 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.