netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Vakul Garg <vakul.garg@nxp.com>
Cc: Florian Westphal <fw@strlen.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: ipsec tunnel performance degrade
Date: Tue, 23 Apr 2019 18:25:21 +0200	[thread overview]
Message-ID: <20190423162521.sn4lfd5iia566f44@breakpoint.cc> (raw)
In-Reply-To: <VE1PR04MB667057A99CCF246A613155378B230@VE1PR04MB6670.eurprd04.prod.outlook.com>

Vakul Garg <vakul.garg@nxp.com> wrote:
> > Vakul Garg <vakul.garg@nxp.com> wrote:
> > > > Do you use xfrm interfaces?
> > >
> > > I don't think so. I use setkey to create policies/SAs.
> > > Can you please give me some hint about it?
> > 
> > Then you're not using ipsec interfaces.
> > 
> Instead of creating policies/SA using setkey, I shifted to using 'ip xfrm' commands.
> With this, I get good performance improvement (20% better in one case).
> Now xfrm_state_find() function is not taking much cpu.

Thats very strange, I have no explanation for this.
It would be good to find the cause, PF_KEY and 'ip xfrm'
are just different control plane frontends, they should have no impact
on data path performance.

> Is this what you meant by 'xfrm interfaces'?

No, i meant the xfrm network interfaces that were added recently, see
net/xfrm/xfrm_interface.c

> > I have no further suggestions.  I don't know yet when I will have time to look
> > into refcnt optimizations.
> > 
> > Idea would be to make them same as dev_hold/put.
> 
> I will try to address it. Can you provide some guidance? Thanks.

I will try to make ugly POC hack tomorrow that should
illustrate the general idea (and caveats/bugs that need fixing).

  reply	other threads:[~2019-04-23 16:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22 14:29 ipsec tunnel performance degrade Vakul Garg
2019-04-22 17:45 ` Florian Westphal
2019-04-23  2:36   ` Vakul Garg
2019-04-23  5:56     ` Florian Westphal
2019-04-23 15:04       ` Vakul Garg
2019-04-23 16:25         ` Florian Westphal [this message]
2019-04-23 17:27           ` David Miller
2019-04-24  7:32             ` Vakul Garg
2019-04-24 10:40           ` [RFC HACK] xfrm: make state refcounting percpu Florian Westphal
2019-04-24 11:38             ` Eric Dumazet
2019-05-03  6:07             ` Steffen Klassert
2019-05-03  6:13               ` Vakul Garg
2019-05-03  6:22                 ` Steffen Klassert
2019-05-03  6:34                   ` Vakul Garg
2019-05-03  6:46                     ` Steffen Klassert
2019-05-03  6:48                       ` Vakul Garg
2019-05-03 12:06               ` Eric Dumazet
2019-05-03 15:55                 ` Florian Westphal

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=20190423162521.sn4lfd5iia566f44@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    --cc=vakul.garg@nxp.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).