From: Saeed Mahameed <saeed@kernel•org>
To: "David S. Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>
Cc: netdev@vger•kernel.org,
"Cc : Steffen Klassert" <steffen.klassert@secunet•com>,
Saeed Mahameed <saeedm@nvidia•com>
Subject: [PATCH net 0/3] Fix ipsec offlaods with vxlan tunnel
Date: Wed, 14 Apr 2021 16:25:37 -0700 [thread overview]
Message-ID: <20210414232540.138232-1-saeed@kernel.org> (raw)
From: Saeed Mahameed <saeedm@nvidia•com>
This small series fixes ipsec TX offloads with vxlan overlay on top of
the offloaded ipsec packet, the driver (mlx5) was lacking such information
and the skb->encapsulation bit wasn't enough as indication to reach the
vxlan inner headers, as a solution we mark the tunnel in the offloaded
context of ipsec.
For more information please see commit messages.
Thanks,
Saeed.
---
Huy Nguyen (3):
net/mlx5: Optimize mlx5e_feature_checks for non IPsec packet
net/xfrm: Add inner_ipproto into sec_path
net/mlx5: Fix checksum issue of VXLAN and IPsec crypto offload
.../mellanox/mlx5/core/en_accel/ipsec_rxtx.c | 65 ++++++++++++++-----
.../mellanox/mlx5/core/en_accel/ipsec_rxtx.h | 34 ++++++++--
.../net/ethernet/mellanox/mlx5/core/en_main.c | 8 ++-
include/net/xfrm.h | 1 +
net/xfrm/xfrm_output.c | 36 +++++++++-
5 files changed, 118 insertions(+), 26 deletions(-)
--
2.30.2
next reply other threads:[~2021-04-14 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 23:25 Saeed Mahameed [this message]
2021-04-14 23:25 ` [PATCH net 1/3] net/mlx5: Optimize mlx5e_feature_checks for non IPsec packet Saeed Mahameed
2021-04-14 23:25 ` [PATCH net 2/3] net/xfrm: Add inner_ipproto into sec_path Saeed Mahameed
2021-04-15 7:47 ` Steffen Klassert
2021-04-15 17:00 ` Jakub Kicinski
2021-04-29 1:50 ` Huy Nguyen
2021-04-14 23:25 ` [PATCH net 3/3] net/mlx5: Fix checksum issue of VXLAN and IPsec crypto offload Saeed Mahameed
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=20210414232540.138232-1-saeed@kernel.org \
--to=saeed@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=saeedm@nvidia$(echo .)com \
--cc=steffen.klassert@secunet$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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