From: Florian Westphal <fw@strlen.de>
To: <netdev@vger.kernel.org>
Subject: [RFC 0/3] ipsec: flow cache removal
Date: Tue, 27 Sep 2016 18:05:20 +0200 [thread overview]
Message-ID: <1474992323-11327-1-git-send-email-fw@strlen.de> (raw)
Please do not apply these patches.
These are part of tests I made for the ipsec workshop at upcoming
netdev 1.2 and I wanted to post these before the conference.
Short version is that there appear to be no major scalability issues
anymore without flow cache. Performance hit can be up to 30%
in my tests (with 64 byte packets), however without flow cache we
also avoid some undesirable effects when flow cache is constantly
overloaded.
Seems most of the extra cost is mainly because of extra xfrm dst
init/destruction (and not e.g. due to policy lookup).
Lets discuss more at the workshop.
Thanks,
Florian
next reply other threads:[~2016-09-27 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 16:05 Florian Westphal [this message]
2016-09-27 16:05 ` [RFC 1/3] xfrm: state: do not acquire lock in get_mtu helpers Florian Westphal
2016-09-27 16:05 ` [RFC 2/3] vti: revert flush x-netns xfrm cache when vti interface is removed Florian Westphal
2016-09-27 16:05 ` [RFC 3/3] xfrm: remove flow cache Florian Westphal
2016-09-28 2:15 ` [RFC 0/3] ipsec: flow cache removal David Miller
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=1474992323-11327-1-git-send-email-fw@strlen.de \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
/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).