From: Steffen Klassert <steffen.klassert@secunet.com>
To: <netdev@vger.kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>
Subject: [PATCH RFC v2 4/5] xfrm: Allow IPsec GSO with software crypto for local sockets.
Date: Fri, 15 Dec 2017 10:13:07 +0100 [thread overview]
Message-ID: <20171215091308.23626-5-steffen.klassert@secunet.com> (raw)
In-Reply-To: <20171215091308.23626-1-steffen.klassert@secunet.com>
With support of async crypto operations in the GSO codepath
we have everything in place to allow GSO for local sockets.
This patch enables the GSO codepath.
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
---
include/net/xfrm.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/net/xfrm.h b/include/net/xfrm.h
index 2517c4f7781a..357764a2bb4e 100644
--- a/include/net/xfrm.h
+++ b/include/net/xfrm.h
@@ -1910,6 +1910,8 @@ static inline bool xfrm_dst_offload_ok(struct dst_entry *dst)
return false;
xdst = (struct xfrm_dst *) dst;
+ if (!x->xso.offload_handle && !xdst->child->xfrm)
+ return true;
if (x->xso.offload_handle && (x->xso.dev == xfrm_dst_path(dst)->dev) &&
!xdst->child->xfrm)
return true;
--
2.14.1
next prev parent 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 [PATCH RFC v2 0/5] Support asynchronous crypto for IPsec GSO Steffen Klassert
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 ` Steffen Klassert [this message]
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-5-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