From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com, Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
Jamal Hadi Salim <hadi@cyberus.ca>
Subject: Re: [patch/RFC]: Asynchronous IPsec processing.
Date: Tue, 03 May 2005 14:18:22 +0400 [thread overview]
Message-ID: <1115115502.3414.22.camel@uganda> (raw)
In-Reply-To: <20050503095312.GA29788@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
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:
> >
> > 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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-03 10:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 10:41 [patch/RFC]: Asynchronous IPsec processing Evgeniy Polyakov
2005-04-30 13:36 ` Evgeniy Polyakov
2005-05-03 9:53 ` Herbert Xu
2005-05-03 10:18 ` Evgeniy Polyakov [this message]
2005-05-03 10:14 ` Herbert Xu
2005-05-03 10:31 ` Evgeniy Polyakov
2005-05-03 10:29 ` Herbert Xu
2005-05-03 10:55 ` Evgeniy Polyakov
2005-05-03 13:38 ` [patch/RFC]: Asynchronous IPsec processing benchmark Evgeniy Polyakov
2005-05-04 10:40 ` jamal
2005-05-04 16:11 ` Evgeniy Polyakov
2005-05-05 13:04 ` jamal
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=1115115502.3414.22.camel@uganda \
--to=johnpol@2ka.mipt.ru \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).