From: Huy Nguyen <huyn@nvidia.com>
To: <netdev@vger.kernel.org>
Cc: <steffen.klassert@secunet.com>, <saeedm@nvidia.com>,
<borisp@nvidia.com>, <raeds@nvidia.com>, <danielj@nvidia.com>,
<yossiku@nvidia.com>, <kuba@kernel.org>, <huyn@nvidia.com>
Subject: [PATCH net-next v4 0/3] Fix IPsec crypto offloads with vxlan tunnel
Date: Mon, 7 Jun 2021 21:00:43 +0300 [thread overview]
Message-ID: <20210607180046.13212-1-huyn@nvidia.com> (raw)
v1 -> v2:
- Move inner_ipproto into xfrm_offload structure.
- Fix static code analysis errors.
- skip checking for skb->encapsulation to be more flexible for vendor
v2 -> v3:
- Fix bug in patch 003 when checking for xo null pointer in mlx5e_ipsec_feature_check
- Fix bug of accidentally commenting out memset in patch 003
v3 -> v4:
- Check explicitly for skb->ecapsulation before calling xfrm_get_inner_ipproto.
- Move patche set to net-next
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 | 37 ++++++++---
.../net/ethernet/mellanox/mlx5/core/en_main.c | 8 ++-
include/net/xfrm.h | 1 +
net/xfrm/xfrm_output.c | 42 +++++++++++-
5 files changed, 125 insertions(+), 28 deletions(-)
--
2.24.1
next reply other threads:[~2021-06-07 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 18:00 Huy Nguyen [this message]
2021-06-07 18:00 ` [PATCH net-next v4 1/3] net/mlx5: Optimize mlx5e_feature_checks for non IPsec packet Huy Nguyen
2021-06-07 18:00 ` [PATCH net-next v4 2/3] net/xfrm: Add inner_ipproto into sec_path Huy Nguyen
2021-06-10 10:36 ` Steffen Klassert
2021-06-07 18:00 ` [PATCH net-next v4 3/3] net/mlx5: Fix checksum issue of VXLAN and IPsec crypto offload Huy Nguyen
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=20210607180046.13212-1-huyn@nvidia.com \
--to=huyn@nvidia.com \
--cc=borisp@nvidia.com \
--cc=danielj@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raeds@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=steffen.klassert@secunet.com \
--cc=yossiku@nvidia.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).