From patchwork Thu Jul 6 02:45:26 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ke Xu X-Patchwork-Id: 129323 X-Patchwork-Delegate: qi.z.zhang@intel.com Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8DF8E42DE1; Thu, 6 Jul 2023 04:45:31 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5818D40144; Thu, 6 Jul 2023 04:45:31 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mails.dpdk.org (Postfix) with ESMTP id ED963400D5; Thu, 6 Jul 2023 04:45:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1688611529; x=1720147529; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=6Qr0Hg2mviSLdyCMxH1ekqYoME4Dawcsd4acMZ2b1Xc=; b=O2+jQoYl90DmNwTNrc1Kixw6Om1EB3dc+gqIOznYScdPNYAsE2WNLWv5 pPtB8g7dNJ+S1I1mO/iBQJXAuLWL2HdgmYvhHx+IK8u6+sQgNitSykz12 Pq4NZDVydRSPAnYk+1J1fSqMl6JngckQkK0aZnFoCUntjV4iixY98HvP1 AdSXpbM+UetHaHfHqz/Ahjh0o7KyHg1HNdY+d/igWkFviY8hmks6CtgXu RMyk3qkbPcwPwnhgFx+4d7Pyu2XbLaw1ngYdvLc7DNfZDKMMWH+zXriaW qstcV1sV+6hbzchz6HVTsncfir29hyoANApsEHe/el6njot96dUS4Na4x Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10762"; a="360962544" X-IronPort-AV: E=Sophos;i="6.01,184,1684825200"; d="scan'208";a="360962544" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jul 2023 19:45:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10762"; a="669606096" X-IronPort-AV: E=Sophos;i="6.01,184,1684825200"; d="scan'208";a="669606096" Received: from dpdk-xuke-host.sh.intel.com ([10.67.114.220]) by orsmga003.jf.intel.com with ESMTP; 05 Jul 2023 19:45:25 -0700 From: Ke Xu 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 Message-Id: <20230706024526.1017993-1-ke1.xu@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230705103538.903685-1-ke1.xu@intel.com> References: <20230705103538.903685-1-ke1.xu@intel.com> MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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 Acked-by: Zhichao Zeng --- 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 ( \