On Tue, May 03, 2005 at 02:18:22PM +0400, Evgeniy Polyakov wrote:

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.

Well if there were no better options then we'll have to do that.

However, I believe that with the right crypto API we should be
able to have async crypto support without sacrificing synchronous
performance.

It looks like several CPUs can not be used for synchronous crypto
processing in current IPsec implementation. Using asynchronous

That's just an implementation quirk.  I will be addressing that
soon as part of the xfrm locking clean-up.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} [off-list ref]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt