From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Raja Zidane <rzidane@nvidia.com>, <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, <stable@dpdk.org>
Subject: Re: [PATCH] app/testpmd: fix GENEVE parsing in csum forward mode
Date: Tue, 18 Jan 2022 09:51:53 +0000 [thread overview]
Message-ID: <4787802c-cefe-6d15-817f-6b906451ded8@intel.com> (raw)
In-Reply-To: <20211205034450.7888-1-rzidane@nvidia.com>
On 12/5/2021 3:44 AM, Raja Zidane wrote:
> The csum FWD mode parses any received packet to set mbuf offloads for the
> transmitting burst, mainly in the checksum/TSO areas.
> In the case of a tunnel header, the csum FWD tries to detect known tunnels
> by the standard definition using the header'sdata and fallback to check the
> packet type in the mbuf to see if the Rx port driver already sign the
> packet as a tunnel.
> In the fallback case, the csum assumes the tunnel is VXLAN and parses the
> tunnel as VXLAN.
As far as I can see there is a VXLAN port check in 'parse_vxlan()', why it
is not helping?
> When the GENEVE tunnel was added to the known tunnels in csum, its parsing
> trial was wrongly located after the pkt type detection, causing the csum to
> parse the GENEVE header as VXLAN when the Rx port set the tunnel packet
> type.
>
> Locate the GENEVE parsing trial before the packet type detection.
>
> Fixes: ea0e711b8ae0 ("app/testpmd: add GENEVE parsing")
> Cc: stable@dpdk.org
>
> Signed-off-by: Raja Zidane <rzidane@nvidia.com>
> ---
> Acked-by: Matan Azrad <matan@nvidia.com>
Ack should be before '---' to be part of the commit log, otherwise it is dropped
when applied as comment.
> app/test-pmd/csumonly.c | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/app/test-pmd/csumonly.c b/app/test-pmd/csumonly.c
> index 2aeea243b6..fe810fecdd 100644
> --- a/app/test-pmd/csumonly.c
> +++ b/app/test-pmd/csumonly.c
> @@ -254,7 +254,10 @@ parse_gtp(struct rte_udp_hdr *udp_hdr,
> info->l2_len += RTE_ETHER_GTP_HLEN;
> }
>
> -/* Parse a vxlan header */
> +/*
> + * Parse a vxlan header.
> + * If a tunnel is detected in 'pkt_type' it will be parsed by default as vxlan.
> + */
> static void
> parse_vxlan(struct rte_udp_hdr *udp_hdr,
> struct testpmd_offload_info *info,
> @@ -912,17 +915,18 @@ pkt_burst_checksum_forward(struct fwd_stream *fs)
> RTE_MBUF_F_TX_TUNNEL_VXLAN_GPE;
> goto tunnel_update;
> }
> - parse_vxlan(udp_hdr, &info,
> - m->packet_type);
> + parse_geneve(udp_hdr, &info);
> if (info.is_tunnel) {
> tx_ol_flags |=
> - RTE_MBUF_F_TX_TUNNEL_VXLAN;
> + RTE_MBUF_F_TX_TUNNEL_GENEVE;
> goto tunnel_update;
> }
> - parse_geneve(udp_hdr, &info);
> + /* Always keep last. */
> + parse_vxlan(udp_hdr, &info,
> + m->packet_type);
> if (info.is_tunnel) {
> tx_ol_flags |=
> - RTE_MBUF_F_TX_TUNNEL_GENEVE;
> + RTE_MBUF_F_TX_TUNNEL_VXLAN;
> goto tunnel_update;
> }
> } else if (info.l4_proto == IPPROTO_GRE) {
next prev parent reply other threads:[~2022-01-18 9:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 3:44 Raja Zidane
2022-01-18 9:51 ` Ferruh Yigit [this message]
2022-01-18 11:27 ` Matan Azrad
2022-01-18 12:28 ` Ferruh Yigit
2022-01-18 12:55 ` Matan Azrad
2022-01-18 13:03 ` Ferruh Yigit
2022-01-18 13:19 ` Matan Azrad
2022-01-20 10:46 ` Singh, Aman Deep
2022-01-30 11:18 ` Raja Zidane
2022-01-31 16:47 ` Singh, Aman Deep
2022-02-15 14:31 ` Raja Zidane
2022-02-15 14:43 ` Singh, Aman Deep
2022-02-16 2:02 ` Xing, Beilei
2022-02-16 12:37 ` [PATCH V2] " Raja Zidane
2022-02-18 9:09 ` Singh, Aman Deep
2022-02-20 12:09 ` [PATCH V3] " Raja Zidane
2022-02-21 10:24 ` Singh, Aman Deep
2022-02-21 12:08 ` Ferruh Yigit
2022-02-21 13:24 ` [PATCH V4] " Raja Zidane
2022-02-21 17:36 ` Ferruh Yigit
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=4787802c-cefe-6d15-817f-6b906451ded8@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rzidane@nvidia.com \
--cc=stable@dpdk.org \
/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).