From: Saeed Mahameed <saeed@kernel.org>
To: Huy Nguyen <huyn@nvidia.com>, netdev@vger.kernel.org
Cc: steffen.klassert@secunet.com, borisp@nvidia.com,
raeds@nvidia.com, danielj@nvidia.com, yossiku@nvidia.com,
kuba@kernel.org
Subject: Re: [PATCH net-next v5 0/3] Fix IPsec crypto offloads with vxlan tunnel
Date: Tue, 22 Jun 2021 14:53:43 -0700 [thread overview]
Message-ID: <6c10216ae0d95aa3fb9e2290830f7196fea9365d.camel@kernel.org> (raw)
In-Reply-To: <20210614143349.74866-1-huyn@nvidia.com>
On Mon, 2021-06-14 at 17:33 +0300, Huy Nguyen wrote:
> v4 -> v5:
> - Fix double initialization of xo in xfrm_get_inner_ipproto
>
> v3 -> v4:
> - Check explicitly for skb->ecapsulation before calling
> xfrm_get_inner_ipproto.
> - Move patche set to net-next
>
> 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
>
> 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
>
> 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.
>
Series applied to net-next-mlx5.
Thanks,
Saeed.
prev parent reply other threads:[~2021-06-22 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 14:33 [PATCH net-next v5 0/3] Fix IPsec crypto offloads with vxlan tunnel Huy Nguyen
2021-06-14 14:33 ` [PATCH net-next v5 1/3] net/mlx5: Optimize mlx5e_feature_checks for non IPsec packet Huy Nguyen
2021-06-14 14:33 ` [PATCH net-next v5 2/3] net/xfrm: Add inner_ipproto into sec_path Huy Nguyen
2021-06-16 5:44 ` Steffen Klassert
2021-06-14 14:33 ` [PATCH net-next v5 3/3] net/mlx5: Fix checksum issue of VXLAN and IPsec crypto offload Huy Nguyen
2021-06-22 21:53 ` Saeed Mahameed [this message]
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=6c10216ae0d95aa3fb9e2290830f7196fea9365d.camel@kernel.org \
--to=saeed@kernel.org \
--cc=borisp@nvidia.com \
--cc=danielj@nvidia.com \
--cc=huyn@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raeds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.