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: [patch/RFC]: Asynchronous IPsec processing benchmark.
Date: Tue, 03 May 2005 17:38:27 +0400 [thread overview]
Message-ID: <1115127507.3414.58.camel@uganda> (raw)
In-Reply-To: <1115117728.3414.48.camel@uganda>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
Here are some numbers:
./netperf -l 60 -H gw -t TCP_STREAM -i 10,2 -I 99,5 -- -m 4096 -s 57344
-S 57344
TCP STREAM TEST to gw : +/-2.5% @ 99% conf.
async-ipsec, 10^6bits/sec: 35.42
sync-ipsec, 10^6bits/sec: 37.11
So even with existing timer deferring it is not noticebly slower [about
4%].
And I think that benefits it provides definitely cost that price and
compile time option.
--
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 13:38 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
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 ` Evgeniy Polyakov [this message]
2005-05-04 10:40 ` [patch/RFC]: Asynchronous IPsec processing benchmark 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=1115127507.3414.58.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).