Thread (12 messages) 12 messages, 3 authors, 2005-05-05

Re: [patch/RFC]: Asynchronous IPsec processing benchmark.

From: jamal <hidden>
Date: 2005-05-04 10:40:14

On Tue, 2005-03-05 at 17:38 +0400, Evgeniy Polyakov wrote:
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%].
by "sync" i hope you mean the original code without your change?

The one thing i see in your POC code that may affect numbers a bit is
allocation of struct esp_async every time in the path. Perhaps precreate
a pool of those and then just grab/return to/fro pool; 
BTW, you may need to incr ref counter of x pre-callback and decrement
when done in callback.
And I think that benefits it provides definitely cost that price and 
compile time option.
I think Herberts concerns about latency should go away if you really
have some proper crypto hardware. 

cheers,
jamal
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help