On Tue, 2005-05-03 at 19:53 +1000, Herbert Xu wrote:

On Fri, Apr 29, 2005 at 02:41:03PM +0400, Evgeniy Polyakov wrote:

quoted

I've created POC code to perform asynchronous IPsec [ESP]
processing. Please comment about bugs in the following patch.
It of course very dirty - but it is only begining, 
I just want to know if approach is right.
Patch was tested with several ssh session and some 
traffic like find / and tcpdump over them.

IMHO we should ensure that the async code path does not adversely
impact synchronous crypto performance.  Most users will be using
synchronous crypto primitives.  Synchronous crypto is also the best
way to utilise VIA Padlock which is arguably the best hardware crypto
solution that's available today.

It can be compile option - those people who wants asynchronous crypto
processing and has appropriate hardware will benefit from that even
if theirs general purpose CPU is VIA with PadLock ACE.

It looks like several CPUs can not be used for synchronous crypto
processing in current IPsec implementation. Using asynchronous
mode there might be significant performance win.

Cheers,

-- 
        Evgeniy Polyakov

Crash is better than data corruption -- Arthur Grabowski