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 v4 2/3] net/xfrm: Add inner_ipproto into sec_path
Date: Thu, 10 Jun 2021 12:36:55 +0200 [thread overview]
Message-ID: <20210610103655.GS40979@gauss3.secunet.de> (raw)
In-Reply-To: <20210607180046.13212-3-huyn@nvidia.com>
On Mon, Jun 07, 2021 at 09:00:45PM +0300, Huy Nguyen wrote:
>
> +/* For partial checksum offload, the outer header checksum is calculated
> + * by software and the inner header checksum is calculated by hardware.
> + * This requires hardware to know the inner packet type to calculate
> + * the inner header checksum. Save inner ip protocol here to avoid
> + * traversing the packet in the vendor's xmit code.
> + * If the encap type is IPIP, just save skb->inner_ipproto. Otherwise,
> + * get the ip protocol from the IP header.
> + */
> +static void xfrm_get_inner_ipproto(struct sk_buff *skb)
> +{
> + struct xfrm_offload *xo = xfrm_offload(skb);
> + const struct ethhdr *eth;
> +
> + xo = xfrm_offload(skb);
You fetched the xo pointer already above.
next prev parent reply other threads:[~2021-06-10 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 18:00 [PATCH net-next v4 0/3] Fix IPsec crypto offloads with vxlan tunnel Huy Nguyen
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 [this message]
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=20210610103655.GS40979@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.