[Top] [All Lists]

Re: Asynchronous crypto layer.

To: Michal Ludvig <michal@xxxxxxxx>
Subject: Re: Asynchronous crypto layer.
From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
Date: Fri, 29 Oct 2004 19:27:41 +0400
Cc: netdev@xxxxxxxxxxx, cryptoapi@xxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.61.0410291636020.25667@xxxxxxxxxxxxxxxx>
Organization: MIPT
References: <1099030958.4944.148.camel@uganda> <1099053738.1024.104.camel@xxxxxxxxxxxxxxxx> <20041029180652.113f0f6e@xxxxxxxxxxxxxxxxxxxx> <41824D9A.3070407@xxxxxxxx> <20041029183606.0b1a0538@xxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.61.0410291636020.25667@xxxxxxxxxxxxxxxx>
Reply-to: johnpol@xxxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Fri, 29 Oct 2004 16:53:30 +0200 (CEST)
Michal Ludvig <michal@xxxxxxxx> wrote:

> On Fri, 29 Oct 2004, Evgeniy Polyakov wrote:
> > > I have a very preliminary driver for FastCrypt PCI board for 3DES at
> > >
> > > 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.
> > 
> > It would be very appreciated>
> Re Hifn - you may be interested in this Linux driver:

Yes, I've seen this patch.
but it was designed to be usefull only in custom MX box, so it has some
design notes that I do not agree with.
> > > 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?
> > 
> > They are both an addendum to each other, 
> > any crypto layer can be "tunrned into compatibility mode" - 
> > i.e. anyone can write bridges like attached sha1_provider.c (it is bridge
> > from async into sync mode). So I can not answer - but in _current_ 
> > implementation without any kind of bridges it is an extension.
> > 
> > If you compile this sources then you will still have old sync behaviour, 
> > IPsec and any other old-style application should be rewritten(like 
> > attached consumer.c) to use new asynchronous crypto layer features.
> This could be a bit of problem, because AFAIK the IPsec code doesn't allow 
> sleeping while processing the packet. It will likely need a bigger 
> rewrite.

It is design issue. In this schema IPsec can not win with acrypto.
but wireless stack, which currently under heavy development, can find acrypto 
very effective.

> Anyway, have you got any tool to measure the cipher throughput without 
> IPsec/dm-crypt being updated for acrypto?

Currently I'm porting from 2.4 my simple block device which was used as 
communicator between host cpu and embedded pci based board.
Probably it can be used as simple measurement tool.
Or even I will write from scratch this weekend simple block device 
like cryptoloop.

> Michal Ludvig
> -- 
> * A mouse is a device used to point at the xterm you want to type in.
> * Personal homepage -

        Evgeniy Polyakov

Only failure makes us experts. -- Theo de Raadt

<Prev in Thread] Current Thread [Next in Thread>