From: Steffen Klassert <steffen.klassert@secunet.com>
To: <netdev@vger.kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Sowmini Varadhan <sowmini.varadhan@oracle.com>,
Ilan Tayari <ilant@mellanox.com>,
"Boris Pismenny" <borisp@mellanox.com>,
Ariel Levkovich <lariel@mellanox.com>,
"Hay, Joshua A" <joshua.a.hay@intel.com>
Subject: [PATCH RFC] IPsec performance optimizations
Date: Fri, 23 Sep 2016 09:53:37 +0200 [thread overview]
Message-ID: <1474617228-26103-1-git-send-email-steffen.klassert@secunet.com> (raw)
This patchset adds several performance optimizations for the ESP IPsec
protocol. This RFC version is intended to be a discussion base for the
IPsec workshop at the netdev 1.2 conference.
The patchset has two parts, patches 1 - 4 are software optimizations.
These patches are complete and could go upstream after some review.
Patch 5 - 11 are needed to create an API for ESP offload to network
devices. Mellanox prepares the mlx5 driver for the use of the created
API, see
https://git.kernel.org/cgit/linux/kernel/git/klassert/linux-stk.git/?h=net-next-ipsec-offload-api3
This part is still under development, changes are very likely before
it can go upstream.
Patch 1 and 2 try to avoid the linearization of ESP packets whenever
possible.
Patch 3 prepares the generic networking codepath for IPsec GRO.
Patch 4 implements software GRO a codepath for ESP on ipv4 and ipv6.
Patch 5 extends the skbuff gso_type to unsigned int. We need a GSO
flag for ESP, but all available gso_type flags are currently in use.
Patch 6 adds the needed netdev features to configure IPsec offloads.
Patch 7 adds gso handlers for esp4 and esp6, currently only used
in combination with ESP hardware offload.
Patch 8 - 9 prepares for IPsec hardware offloading.
Patch 10 implements an IPsec hardware offloading API.
Patch 11 allows for TSO and checksum offloading of the inner IPsec packet.
next reply other threads:[~2016-09-23 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 7:53 Steffen Klassert [this message]
2016-09-23 7:53 ` [PATCH RFC 01/11] esp4: Avoid skb_cow_data whenever possible Steffen Klassert
2016-09-23 7:53 ` [PATCH RFC 02/11] esp6: " Steffen Klassert
2016-09-23 7:53 ` [PATCH RFC 03/11] net: Prepare for IPsec GRO Steffen Klassert
2016-09-23 7:53 ` [PATCH RFC 04/11] esp: Add a software GRO codepath Steffen Klassert
2016-09-23 7:53 ` [PATCH RFC 05/11] skbuff: Extend gso_type to unsigned int Steffen Klassert
2016-09-23 13:19 ` David Laight
2016-09-23 15:15 ` Alexander Duyck
2016-09-23 7:53 ` [PATCH RFC 06/11] net: Add ESP offload features Steffen Klassert
2016-09-23 7:53 ` [PATCH RFC 07/11] esp: Add gso handlers for esp4 and esp6 Steffen Klassert
2016-09-23 7:53 ` [PATCH RFC 08/11] xfrm: Move device notifications to a sepatate file Steffen Klassert
2016-09-23 7:53 ` [PATCH RFC 09/11] xfrm: Add an IPsec hardware offloading API Steffen Klassert
2016-09-23 7:53 ` [PATCH RFC 10/11] xfrm: Add xfrm_replay_overflow functions for offloading Steffen Klassert
2016-09-23 7:53 ` [PATCH RFC 11/11] xfrm: Add encapsulation header offsets while SKB is not encrypted 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=1474617228-26103-1-git-send-email-steffen.klassert@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=borisp@mellanox.com \
--cc=ilant@mellanox.com \
--cc=joshua.a.hay@intel.com \
--cc=lariel@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.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