From: Steffen Klassert <steffen.klassert@secunet.com>
To: Timo Teras <timo.teras@iki.fi>
Cc: Andrew Collins <bsderandrew@gmail.com>, netdev@vger.kernel.org
Subject: Re: ipsec smp scalability and cpu use fairness (softirqs)
Date: Tue, 20 Aug 2013 08:19:14 +0200 [thread overview]
Message-ID: <20130820061914.GA26773@secunet.com> (raw)
In-Reply-To: <20130813154102.35739102@vostro>
On Tue, Aug 13, 2013 at 03:41:02PM +0300, Timo Teras wrote:
> On Tue, 13 Aug 2013 13:56:52 +0200
> Steffen Klassert <steffen.klassert@secunet.com> wrote:
>
> >
> > I'll do some tests with current net-next on my own tomorrow and let
> > you know about the results.
>
> Yes, I've got pcrypt there. Apparently I had some of the cpu bindings
> not right, so now it's looking a lot better. But it seems that
> ksoftirqd on one of the CPUs becomes first bottleneck. I'll try to
> figure out why.
>
> Thanks on all the info so far, will continue experimenting here too.
Here are the promised test results:
I used my test boxes with two nodes (Intel Xeon X5550 @ 2.67GHz) and all
cores utilized (16 logical cores). I did iperf box to box IPsec tunnel
tests with the crypto algorithm:
pcrypt(authenc(hmac(sha1-ssse3),cbc(aes-asm)))
Throughput is at 1.70 Gbits/sec.
Same test without pcrypt, i.e. crypto algorithm:
authenc(hmac(sha1-ssse3),cbc(aes-asm))
Throughput is at 560 Mbits/sec.
Unfortunately I can't do forwarding tests, I have only two 10 Gbit NICs.
Would be nice if I could get forwarding test results from somewhere.
next prev parent reply other threads:[~2013-08-20 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 13:01 ipsec smp scalability and cpu use fairness (softirqs) Timo Teras
2013-08-12 21:58 ` Andrew Collins
2013-08-13 6:23 ` Timo Teras
2013-08-13 7:46 ` Steffen Klassert
2013-08-13 7:57 ` Timo Teras
2013-08-13 10:45 ` Steffen Klassert
2013-08-13 11:33 ` Timo Teras
2013-08-13 11:56 ` Steffen Klassert
2013-08-13 12:41 ` Timo Teras
2013-08-20 6:19 ` Steffen Klassert [this message]
2013-08-20 6:39 ` Timo Teras
2013-08-20 6:17 ` Steffen Klassert
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=20130820061914.GA26773@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=bsderandrew@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=timo.teras@iki.fi \
/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).