From: Michal Ludvig <michal@logix.cz>
To: johnpol@2ka.mipt.ru
Cc: hadi@cyberus.ca, netdev@oss.sgi.com, cryptoapi@lists.logix.cz
Subject: Re: Asynchronous crypto layer.
Date: Fri, 29 Oct 2004 16:03:06 +0200 [thread overview]
Message-ID: <41824D9A.3070407@logix.cz> (raw)
In-Reply-To: <20041029180652.113f0f6e@zanzibar.2ka.mipt.ru>
Evgeniy Polyakov told me that:
> On 29 Oct 2004 08:42:18 -0400
> jamal <hadi@cyberus.ca> wrote:
>
>>>I am very curious if you see perfomance improvements over old scheme
>>in the case of a single crypto chip in a fast CPU.
>>It has been shown in the past that with a xeon in the range of 2Ghz the
>>context setup and the big lock (and lack of async) implied that
>>performance enhancement using a crypto chip was negligible.
>>IIRC, the only time it started showing anything useful was when a
>>compute intensive alg like 3DES was chewing packets >= 1000 bytes.
>>
>>My suspicion is you will show it is better to use a crypto chip with
>>async;-> In the minimal you should show some improvement.
>
>
> If we have a hardware accelerator chip, than we _already_ have improvements
> with even the worst async crypto layer, since software and hardware
> will work in parrallel.
> I agree that multigigahertz box will beat my HIFN card,
> but I doubt it can beat 1gghz VIA.
I have a very preliminary driver for FastCrypt PCI board for 3DES at
http://www.logix.cz/michal/devel/fcrypt/
For now it works with some very ugly hacks in the current cryptoapi, but
I can give it a try with your acrypto and report the results.
I admit I haven't read your sources too deeply yet so excuse me a dumb
question - does acrypto replace or extend cryptoapi? Once I get it
running will it take over e.g. encryption for IPsec?
Michal Ludvig
--
* A mouse is a device used to point at the xterm you want to type in.
* Personal homepage - http://www.logix.cz/michal
next prev parent reply other threads:[~2004-10-29 14:03 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 6:22 Asynchronous crypto layer Evgeniy Polyakov
2004-10-29 12:42 ` jamal
2004-10-29 14:06 ` Evgeniy Polyakov
2004-10-29 14:03 ` Michal Ludvig [this message]
2004-10-29 14:36 ` Evgeniy Polyakov
2004-10-29 14:53 ` Michal Ludvig
2004-10-29 15:11 ` jamal
2004-10-29 15:27 ` Evgeniy Polyakov
2004-10-30 20:39 ` Eugene Surovegin
2004-10-30 21:17 ` Evgeniy Polyakov
2004-10-30 21:09 ` Eugene Surovegin
2004-10-30 21:46 ` Evgeniy Polyakov
2004-10-29 15:08 ` jamal
2004-10-29 15:37 ` Evgeniy Polyakov
2004-10-29 15:28 ` Michal Ludvig
2004-10-29 16:16 ` James Morris
2004-10-29 16:45 ` Evgeniy Polyakov
2004-10-29 20:00 ` Sam Leffler
2004-10-31 6:09 ` James Morris
2004-10-31 6:35 ` Sam Leffler
2004-10-30 20:35 ` Eugene Surovegin
2004-10-30 21:04 ` Evgeniy Polyakov
2004-10-30 20:56 ` Eugene Surovegin
2004-10-30 21:24 ` Evgeniy Polyakov
2004-10-30 23:41 ` jamal
2004-10-31 9:13 ` Evgeniy Polyakov
2004-10-31 10:46 ` Michal Ludvig
2004-10-31 15:03 ` jamal
2004-10-31 16:07 ` James Morris
2004-11-01 6:01 ` Evgeniy Polyakov
2004-10-31 15:36 ` Michael Richardson
2004-10-31 16:09 ` James Morris
2004-10-31 14:56 ` jamal
2004-11-01 5:12 ` Evgeniy Polyakov
2004-10-29 17:44 ` James Morris
2004-10-29 17:46 ` James Morris
2004-10-30 5:20 ` Evgeniy Polyakov
2004-10-31 5:43 ` James Morris
2004-10-30 5:19 ` Evgeniy Polyakov
2004-10-30 8:34 ` Evgeniy Polyakov
2004-10-30 8:36 ` Evgeniy Polyakov
2004-10-30 16:57 ` Michal Ludvig
2004-10-30 17:40 ` Evgeniy Polyakov
2004-10-30 20:17 ` Michal Ludvig
2004-10-30 20:56 ` Evgeniy Polyakov
2004-10-30 19:42 ` James Morris
2004-10-29 19:56 ` Sam Leffler
2004-10-30 6:16 ` Christoph Hellwig
2004-10-30 20:37 ` Evgeniy Polyakov
2004-10-31 16:05 ` James Morris
2004-11-01 5:58 ` Evgeniy Polyakov
2004-12-14 6:56 ` James Morris
2004-12-14 7:58 ` Evgeniy Polyakov
2004-11-02 15:24 ` Evgeniy Polyakov
2004-11-02 16:12 ` Evgeniy Polyakov
2004-12-14 7:23 ` James Morris
2004-12-14 8:07 ` Evgeniy Polyakov
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=41824D9A.3070407@logix.cz \
--to=michal@logix.cz \
--cc=cryptoapi@lists.logix.cz \
--cc=hadi@cyberus.ca \
--cc=johnpol@2ka.mipt.ru \
--cc=netdev@oss.sgi.com \
/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.