From: Florian Westphal <fw@strlen.de>
To: steffen.klassert@secunet.com
Cc: <netdev@vger.kernel.org>
Subject: [PATCH ipsec-next v2 0/7] xfrm: remove three more indirect calls from packet path
Date: Mon, 4 May 2020 10:06:02 +0200 [thread overview]
Message-ID: <20200504080609.14648-1-fw@strlen.de> (raw)
v2: rebase on top of ipsec-next, no other changes.
This patch series removes three more indirect calls from the state_afinfo
struct.
These are:
- extract_input (no dependencies on other modules)
- output_finish (same)
- extract_output (has dependency on ipv6 module, but
that is only needed for pmtu detection, so the indirect
call cost is not required for each packet).
Functions get moved to net/xfrm and the indirections are removed.
pmtu detection will be handled via ipv6_stubs.
Florian Westphal (7):
xfrm: avoid extract_output indirection for ipv4
xfrm: state: remove extract_input indirection from xfrm_state_afinfo
xfrm: move xfrm4_extract_header to common helper
xfrm: expose local_rxpmtu via ipv6_stubs
xfrm: place xfrm6_local_dontfrag in xfrm.h
xfrm: remove extract_output indirection from xfrm_state_afinfo
xfrm: remove output_finish indirection from xfrm_state_afinfo
include/net/ipv6_stubs.h | 1 +
include/net/xfrm.h | 26 ++++++----
net/ipv4/xfrm4_input.c | 5 --
net/ipv4/xfrm4_output.c | 63 +----------------------
net/ipv4/xfrm4_state.c | 24 ---------
net/ipv6/af_inet6.c | 1 +
net/ipv6/xfrm6_input.c | 5 --
net/ipv6/xfrm6_output.c | 98 ++---------------------------------
net/ipv6/xfrm6_state.c | 26 ----------
net/xfrm/xfrm_inout.h | 32 ++++++++++++
net/xfrm/xfrm_input.c | 21 ++++----
net/xfrm/xfrm_output.c | 129 ++++++++++++++++++++++++++++++++++++++++++++---
12 files changed, 188 insertions(+), 243 deletions(-)
next reply other threads:[~2020-05-04 8:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 8:06 Florian Westphal [this message]
2020-05-04 8:06 ` [PATCH ipsec-next v2 1/7] xfrm: avoid extract_output indirection for ipv4 Florian Westphal
2020-05-04 8:06 ` [PATCH ipsec-next v2 2/7] xfrm: state: remove extract_input indirection from xfrm_state_afinfo Florian Westphal
2020-05-04 8:06 ` [PATCH ipsec-next v2 3/7] xfrm: move xfrm4_extract_header to common helper Florian Westphal
2020-05-04 8:06 ` [PATCH ipsec-next v2 4/7] xfrm: expose local_rxpmtu via ipv6_stubs Florian Westphal
2020-05-04 8:06 ` [PATCH ipsec-next v2 5/7] xfrm: place xfrm6_local_dontfrag in xfrm.h Florian Westphal
2020-05-04 8:06 ` [PATCH ipsec-next v2 6/7] xfrm: remove extract_output indirection from xfrm_state_afinfo Florian Westphal
2020-05-04 8:06 ` [PATCH ipsec-next v2 7/7] xfrm: remove output_finish " Florian Westphal
2020-05-08 8:42 ` [PATCH ipsec-next v2 0/7] xfrm: remove three more indirect calls from packet path 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=20200504080609.14648-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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).