From: Jean-Luc Cooke <jlcooke@certainkey.com>
To: Jari Ruusu <jari.ruusu@pp.inet.fi>
Cc: 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: Thu, 24 Oct 2002 10:50:26 -0400 [thread overview]
Message-ID: <20021024105026.C1170@certainkey.com> (raw)
In-Reply-To: <3DB4DBC8.8647E32E@pp.inet.fi>; from jari.ruusu@pp.inet.fi on Tue, Oct 22, 2002 at 08:02:00AM +0300
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
JLC
--
http://www.certainkey.com
Suite 4560 CTTC
1125 Colonel By Dr.
Ottawa ON, K1S 5B6
C: 613.263.2983
next prev parent reply other threads:[~2002-10-24 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 8:05 [PATCH] USAGI IPsec Mitsuru KANDA
2002-10-12 17:11 ` [Design] " Sandy Harris
2002-10-12 2:27 ` David S. Miller
2002-10-19 1:40 ` Zach Brown
2002-10-21 14:46 ` 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 [this message]
2002-10-28 13:55 ` JuanJo Ciarlante
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=20021024105026.C1170@certainkey.com \
--to=jlcooke@certainkey.com \
--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=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 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.