netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "JuanJo Ciarlante" <jjo-ipsec@mendoza.gov.ar>
To: Jean-Luc Cooke <jlcooke@certainkey.com>
Cc: Jari Ruusu <jari.ruusu@pp.inet.fi>,
	Herbert Valerio Riedel <hvr@hvrlab.org>,
	"David S. Miller" <davem@rth.ninka.net>,
	Sandy Harris <sandy@storm.ca>, Mitsuru KANDA <mk@linux-ipv6.org>,
	linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	cryptoapi-devel@kerneli.org, design@lists.freeswan.org,
	usagi@linux-ipv6.org
Subject: Re: [CryptoAPI-devel] Re: [Design] [PATCH] USAGI IPsec
Date: Mon, 28 Oct 2002 10:55:25 -0300	[thread overview]
Message-ID: <20021028105525.C18414@mendoza.gov.ar> (raw)
In-Reply-To: <20021024105026.C1170@certainkey.com>; from jlcooke@certainkey.com on Thu, Oct 24, 2002 at 10:50:26AM -0400

On Thu, Oct 24, 2002 at 10:50:26AM -0400, Jean-Luc Cooke wrote:
> On Tue, Oct 22, 2002 at 08:02:00AM +0300, Jari Ruusu wrote:
> > kerneli.org/cryptoapi _is_ useless joke for many needs. Fortunately other
> > people are able to see the limitations/sillyness of kerneli.org/cryptoapi:
> > 
> > 1)  You are trying to replace link/insmod time overhead with runtime
> >     overhead + unnecessary bloat.
> > 2)  No direct link access to low level cipher functions or higher level
> >     functions.
> > 3)  No clean way to replace cipher code with processor type optimized
> >     assembler implementations.
> 
> Jari has a few points here.  But the "killer" functionalities are all there
> IMHO.  Low-level assembler implementations are over-rated, again IMHO.  The
> performance difference between C and ASM is at most 50%.  1ms vs 1.5 ms.
> Even if you've got a large payload on the rare occation (>5MB) block ciphers
> are quite fast for 95% of applications

According to my tests, AES ASM has given me _2x_ speed boost over C; this
fact has re-written freeswan CPU/bandwidth empirical formula to peak at
       CPU [MHz] ~= BW [Mbit/s] * 10      (instead of 25)

This boost has allowed my old Cyrix-6x86 120MHz to be my 802.11b gateway  =)


--Juanjo       freeswan algo: AES (+others), SHA2, MODP2048-4096 
               selectable algorithms support for Phase1 and 2.
	       http://www.irrigacion.gov.ar/juanjo/ipsec/

#  Juan Jose Ciarlante (JuanJo PGP) jjo ;at; mendoza.gov.ar              #
#  Key fingerprint = 76 60 A5 76 FD D2 53 E3  50 C7 90 20 22 8C F1 2D    #

  reply	other threads:[~2002-10-28 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11  8:05 [PATCH] USAGI IPsec Mitsuru KANDA
2002-10-21 14:46 ` [Design] " Sandy Harris
2002-10-21  2:41   ` David S. Miller
2002-10-21  3:42     ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-21  7:34     ` [CryptoAPI-devel] " Herbert Valerio Riedel
2002-10-22  2:27       ` Sandy Harris
2002-10-22  5:02       ` Jari Ruusu
2002-10-24 14:50         ` Jean-Luc Cooke
2002-10-28 13:55           ` JuanJo Ciarlante [this message]
2002-10-21  4:22   ` Andre Hedrick

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=20021028105525.C18414@mendoza.gov.ar \
    --to=jjo-ipsec@mendoza.gov.ar \
    --cc=cryptoapi-devel@kerneli.org \
    --cc=davem@rth.ninka.net \
    --cc=design@lists.freeswan.org \
    --cc=hvr@hvrlab.org \
    --cc=jari.ruusu@pp.inet.fi \
    --cc=jlcooke@certainkey.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mk@linux-ipv6.org \
    --cc=netdev@oss.sgi.com \
    --cc=sandy@storm.ca \
    --cc=usagi@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).