From: Steffen Klassert <steffen.klassert@secunet.com>
To: <netdev@vger.kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>
Subject: [PATCH RFC v2 0/5] Support asynchronous crypto for IPsec GSO.
Date: Fri, 15 Dec 2017 10:13:03 +0100 [thread overview]
Message-ID: <20171215091308.23626-1-steffen.klassert@secunet.com> (raw)
This patchset implements asynchronous crypto handling
in the layer 2 TX path. With this we can allow IPsec
ESP GSO for software crypto. This also merges the IPsec
GSO and non-GSO paths to both use validate_xmit_xfrm().
1) Separate ESP handling from segmentation for GRO packets.
This unifies the IPsec GSO and non GSO codepath.
2) Add asynchronous callbacks for xfrm on layer 2. This
adds the necessary infrastructure to core networking.
3) Allow to use the layer2 IPsec GSO codepath for software
crypto, all infrastructure is there now.
4) Also allow IPsec GSO with software crypto for local sockets.
5) Don't require synchronous crypto fallback on IPsec offloading,
it is not needed anymore.
I plan to merge this to ipsec-next during this development cycle.
Changes from v1:
- Resolve conflicts with the lockless qdisc patchset.
- Fix compilation error when CONFIG_XFRM is not set.
- Order local local variables of new functions in reverse christmas
tree ordering.
next reply other threads:[~2017-12-15 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 9:13 Steffen Klassert [this message]
2017-12-15 9:13 ` [PATCH RFC v2 1/5] xfrm: Separate ESP handling from segmentation for GRO packets Steffen Klassert
2017-12-15 9:13 ` [PATCH RFC v2 2/5] net: Add asynchronous callbacks for xfrm on layer 2 Steffen Klassert
2017-12-15 9:13 ` [PATCH RFC v2 3/5] xfrm: Allow to use the layer2 IPsec GSO codepath for software crypto Steffen Klassert
2017-12-15 9:13 ` [PATCH RFC v2 4/5] xfrm: Allow IPsec GSO with software crypto for local sockets Steffen Klassert
2017-12-15 9:13 ` [PATCH RFC v2 5/5] esp: Don't require synchronous crypto fallback on offloading anymore Steffen Klassert
2017-12-21 6:39 ` [PATCH RFC v2 0/5] Support asynchronous crypto for IPsec GSO 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=20171215091308.23626-1-steffen.klassert@secunet.com \
--to=steffen.klassert@secunet.com \
--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