All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Huy Nguyen <huyn@nvidia.com>
Cc: <netdev@vger.kernel.org>, <saeedm@nvidia.com>,
	<borisp@nvidia.com>, <raeds@nvidia.com>, <danielj@nvidia.com>,
	<yossiku@nvidia.com>, <kuba@kernel.org>
Subject: Re: [PATCH net-next v5 2/3] net/xfrm: Add inner_ipproto into sec_path
Date: Wed, 16 Jun 2021 07:44:50 +0200	[thread overview]
Message-ID: <20210616054450.GE40979@gauss3.secunet.de> (raw)
In-Reply-To: <20210614143349.74866-3-huyn@nvidia.com>

On Mon, Jun 14, 2021 at 05:33:48PM +0300, Huy Nguyen wrote:
> The inner_ipproto saves the inner IP protocol of the plain
> text packet. This allows vendor's IPsec feature making offload
> decision at skb's features_check and configuring hardware at
> ndo_start_xmit.
> 
> For example, ConnectX6-DX IPsec device needs the plaintext's
> IP protocol to support partial checksum offload on
> VXLAN/GENEVE packet over IPsec transport mode tunnel.
> 
> Signed-off-by: Raed Salem <raeds@nvidia.com>
> Signed-off-by: Huy Nguyen <huyn@nvidia.com>
> Cc: Steffen Klassert <steffen.klassert@secunet.com>

In case you want to route this through the mlx5 tree:

Acked-by: Steffen Klassert <steffen.klassert@secunet.com>

  reply	other threads:[~2021-06-16  5:44 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 [this message]
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 ` [PATCH net-next v5 0/3] Fix IPsec crypto offloads with vxlan tunnel 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=20210616054450.GE40979@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --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=saeedm@nvidia.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.