From: Ke Xu <ke1.xu@intel.com>
To: dev@dpdk.org
Cc: ke1.xu@intel.com, zhichaox.zeng@intel.com, wenzhuo.lu@intel.com,
stable@dpdk.org
Subject: [PATCH v2] net/iavf: fix Tunnel TSO path selecting.
Date: Thu, 6 Jul 2023 02:45:26 +0000 [thread overview]
Message-ID: <20230706024526.1017993-1-ke1.xu@intel.com> (raw)
In-Reply-To: <20230705103538.903685-1-ke1.xu@intel.com>
IAVF currently supports TSO and Tunnel TSO. Both these two features
are implemented in scalar path. As there are missed flags for Tunnel
TSO, it selects vector paths wrongly when only Tunnel TSO is enabled
after introducing the patch "net/iavf: add offload path for Tx AVX512".
This patch added the missed flags to fix the Tunnel TSO path selecting.
Fixes: 059f18ae2aec ("net/iavf: add offload path for Tx AVX512")
Cc: stable@dpdk.org
Signed-off-by: Ke Xu <ke1.xu@intel.com>
---
v2: Add fixline, add CC, fix commit message.
---
drivers/net/iavf/iavf_rxtx.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/iavf/iavf_rxtx.h b/drivers/net/iavf/iavf_rxtx.h
index 8d4a77271a..605ea3f824 100644
--- a/drivers/net/iavf/iavf_rxtx.h
+++ b/drivers/net/iavf/iavf_rxtx.h
@@ -31,6 +31,10 @@
RTE_ETH_TX_OFFLOAD_QINQ_INSERT | \
RTE_ETH_TX_OFFLOAD_MULTI_SEGS | \
RTE_ETH_TX_OFFLOAD_TCP_TSO | \
+ RTE_ETH_TX_OFFLOAD_VXLAN_TNL_TSO | \
+ RTE_ETH_TX_OFFLOAD_GRE_TNL_TSO | \
+ RTE_ETH_TX_OFFLOAD_IPIP_TNL_TSO | \
+ RTE_ETH_TX_OFFLOAD_GENEVE_TNL_TSO | \
RTE_ETH_TX_OFFLOAD_SECURITY)
#define IAVF_TX_VECTOR_OFFLOAD ( \
--
2.34.1
next prev parent reply other threads:[~2023-07-06 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 10:35 [PATCH] " Ke Xu
2023-07-06 2:45 ` Ke Xu [this message]
2023-07-06 6:07 ` [PATCH v2] " Zeng, ZhichaoX
2023-07-06 6:29 ` Zhang, Qi Z
2023-07-06 2:34 Ke Xu
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=20230706024526.1017993-1-ke1.xu@intel.com \
--to=ke1.xu@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.com \
--cc=zhichaox.zeng@intel.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).