netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: Tom Herbert <tom@herbertland.com>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: ipsec impact on performance
Date: Wed, 2 Dec 2015 08:25:11 -0500	[thread overview]
Message-ID: <20151202132511.GL23178@oracle.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1CBE0F39@AcuExch.aculab.com>

On (12/02/15 12:41), David Laight wrote:
> 
> Also what/how are you measuring cpu use.
> I'm not sure anything on Linux gives you a truly accurate value
> when processes are running for very short periods.

I was using mpstat, while running iperf. Should I be using
something else? or running it for longer intervals?

but I hope we are not doomed at 1 Gbps, or else security itself would
come at a very unattractive cost. Anyway, even aside from crypto.
we need to have some way to add TCP options (that depend on the 
contents of the tcp header) etc post-GSO, in the interest of not 
ossifying the stack.

> On an SMP system you also get big effects when work is switched
> between cpus. I've got some tests that run a lot faster if I
> put all but one of the cpus into a busy-loop in userspace
> (eg: while :; do :; done)!

yes Rick Jones also pointed the same thing to me, and one of the
things I was going to try out later today is to instrument the
effects of pinning irqs and iperf threads to a specific cpu.

--Sowmini

  reply	other threads:[~2015-12-02 13:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 17:59 ipsec impact on performance Sowmini Varadhan
2015-12-01 18:17 ` Rick Jones
2015-12-01 18:45   ` Sowmini Varadhan
2015-12-01 18:50     ` Rick Jones
2015-12-01 19:01       ` Sowmini Varadhan
2015-12-02  0:56   ` David Ahern
2015-12-02  1:09     ` Sowmini Varadhan
2015-12-02  1:25       ` David Ahern
2015-12-01 18:18 ` Tom Herbert
2015-12-01 18:37   ` Sowmini Varadhan
2015-12-02 11:56     ` David Laight
2015-12-02 12:11       ` Sowmini Varadhan
2015-12-02 12:41         ` David Laight
2015-12-02 13:25           ` Sowmini Varadhan [this message]
2015-12-02 20:50           ` Sowmini Varadhan
2015-12-02 21:07             ` Tom Herbert
2015-12-02 21:12               ` Sowmini Varadhan
2015-12-02 21:44                 ` Tom Herbert
2015-12-02 21:47                   ` Sowmini Varadhan
2015-12-02 22:01                     ` Tom Herbert
2015-12-02 22:08                       ` Sowmini Varadhan
2015-12-02 22:25                 ` Eric Dumazet
2015-12-03  1:31       ` Rick Jones
2015-12-02  6:53 ` Steffen Klassert
2015-12-02 12:05   ` Sowmini Varadhan
2015-12-03  8:45     ` Steffen Klassert
2015-12-03 11:38       ` Sowmini Varadhan
2015-12-03 11:47         ` Steffen Klassert
2015-12-07  8:40         ` Steffen Klassert
2015-12-07 11:27           ` Sowmini Varadhan
2015-12-08 11:32             ` Steffen Klassert
2015-12-08 11:51               ` Sowmini Varadhan
2015-12-03 19:33 ` David Miller
2015-12-03 20:08   ` Eric Dumazet
2015-12-03 20:32   ` Sowmini Varadhan
2015-12-04  5:18 ` Sandy Harris

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=20151202132511.GL23178@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=linux-crypto@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tom@herbertland.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).