From: yang_y_yi <yang_y_yi@163.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Hu, Jiayu" <jiayu.hu@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"yangyi01@inspur.com" <yangyi01@inspur.com>
Subject: Re: [dpdk-dev] [PATCH v2] gso: add VXLAN UDP GSO support
Date: Mon, 16 Nov 2020 08:50:21 +0800 (CST) [thread overview]
Message-ID: <5a8b5f03.6ab.175ce8800cc.Coremail.yang_y_yi@163.com> (raw)
In-Reply-To: <DM6PR11MB3308A8F493FC43A19B79B99C9AE60@DM6PR11MB3308.namprd11.prod.outlook.com>
At 2020-11-13 21:16:38, "Ananyev, Konstantin" <konstantin.ananyev@intel.com> wrote:
>...
>> diff --git a/lib/librte_gso/rte_gso.c b/lib/librte_gso/rte_gso.c
>> index 896350e..fb76a21 100644
>> --- a/lib/librte_gso/rte_gso.c
>> +++ b/lib/librte_gso/rte_gso.c
>> @@ -11,6 +11,7 @@
>> #include "gso_common.h"
>> #include "gso_tcp4.h"
>> #include "gso_tunnel_tcp4.h"
>> +#include "gso_tunnel_udp4.h"
>> #include "gso_udp4.h"
>>
>> #define ILLEGAL_UDP_GSO_CTX(ctx) \
>> @@ -60,6 +61,13 @@
>> ret = gso_tunnel_tcp4_segment(pkt, gso_size, ipid_delta,
>> direct_pool, indirect_pool,
>> pkts_out, nb_pkts_out);
>> + } else if (IS_IPV4_VXLAN_UDP4(pkt->ol_flags) &&
>> + (gso_ctx->gso_types & (DEV_TX_OFFLOAD_VXLAN_TNL_TSO |
>> + DEV_TX_OFFLOAD_UDP_TSO))) {
>
>That check would succeed even if DEV_TX_OFFLOAD_VXLAN_TNL_TSO flag is not set.
>Is it supposed to be like that?
Thanks Konstantin for pointing out this, it should be
(gso_ctx->gso_types & DEV_TX_OFFLOAD_VXLAN_TNL_TSO) &&
(gso_ctx->gso_types & DEV_TX_OFFLOAD_UDP_TSO)) {
I'll send out v3 with this correctness.
>
>
>> + pkt->ol_flags &= (~PKT_TX_UDP_SEG);
>> + ret = gso_tunnel_udp4_segment(pkt, gso_size,
>> + direct_pool, indirect_pool,
>> + pkts_out, nb_pkts_out);
>> } else if (IS_IPV4_TCP(pkt->ol_flags) &&
>> (gso_ctx->gso_types & DEV_TX_OFFLOAD_TCP_TSO)) {
>> pkt->ol_flags &= (~PKT_TX_TCP_SEG);
>> --
>> 1.8.3.1
next prev parent reply other threads:[~2020-11-16 0:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 6:46 [dpdk-dev] [PATCH] " yang_y_yi
2020-09-27 5:57 ` yang_y_yi
2020-10-29 6:47 ` [dpdk-dev] [PATCH v1] " yang_y_yi
2020-11-06 4:09 ` Jiayu Hu
2020-11-09 1:03 ` yang_y_yi
2020-11-10 2:21 ` [dpdk-dev] [PATCH v2] " yang_y_yi
2020-11-13 13:16 ` Ananyev, Konstantin
2020-11-16 0:50 ` yang_y_yi [this message]
2020-11-16 1:11 ` [dpdk-dev] [PATCH v3] " yang_y_yi
2020-11-19 5:37 ` Hu, Jiayu
2020-11-19 6:43 ` [dpdk-dev] [PATCH v4] gso: add VXLAN UDP/IPv4 support yang_y_yi
2020-11-19 6:49 ` Hu, Jiayu
2021-01-15 3:51 ` yang_y_yi
2021-01-15 10:24 ` Thomas Monjalon
2021-01-18 0:05 ` yang_y_yi
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=5a8b5f03.6ab.175ce8800cc.Coremail.yang_y_yi@163.com \
--to=yang_y_yi@163.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=thomas@monjalon.net \
--cc=yangyi01@inspur.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).