Message ID | 20231214065857.2142565-1-zhichaox.zeng@intel.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> 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 9A79E436E9; Thu, 14 Dec 2023 07:49:37 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7CCB5402E6; Thu, 14 Dec 2023 07:49:37 +0100 (CET) Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.10]) by mails.dpdk.org (Postfix) with ESMTP id B18E240285 for <dev@dpdk.org>; Thu, 14 Dec 2023 07:49:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1702536576; x=1734072576; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=SQZZv4/yJKkYsxcDfExgl1soGzxKMVvbVmgcWuxJv5I=; b=JWQRXKTFsB/zvUb6ZcVYzfiewq+KuS9ifEa5XDtM7txsT/YeS2yWPuW5 iAv41+jE9jGioPrOKwFwIZVA8GQImiIrIy7rWeV9DDgY6qsrgI2WPmh4X rCHcMEPGxj17nkCjYYYbqWkD48DnsqjZudCy9H8J2VSyd+9i/QaBC9Fao Xs6sdTL2zJv4NF6MabLIBBMti3PZWdN63Xv9rNxhfHLh/S9ZkK2TibVgH 2gPKEgsPfVQXgxCV09hQeFVxC9TYl2fKHzgw73EI+XJqrzcanAt2x8Tnf bdPsuoLIETj0RVt4AcTWaCuhwGL2CzK5yzFejov+MteGHqYU2hnyOIA6F w==; X-IronPort-AV: E=McAfee;i="6600,9927,10923"; a="8440316" X-IronPort-AV: E=Sophos;i="6.04,274,1695711600"; d="scan'208";a="8440316" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orvoesa102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Dec 2023 22:49:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10923"; a="1105584380" X-IronPort-AV: E=Sophos;i="6.04,274,1695711600"; d="scan'208";a="1105584380" Received: from unknown (HELO zhichao-dpdk..) ([10.239.252.103]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Dec 2023 22:49:33 -0800 From: Zhichao Zeng <zhichaox.zeng@intel.com> To: dev@dpdk.org Cc: qi.z.zhang@intel.com, Zhichao Zeng <zhichaox.zeng@intel.com> Subject: [PATCH v2 0/3] net/iavf: support Tx LLDP on scalar and AVX512 Date: Thu, 14 Dec 2023 14:58:54 +0800 Message-Id: <20231214065857.2142565-1-zhichaox.zeng@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20231206060828.3310347-1-zhichaox.zeng@intel.com> References: <20231206060828.3310347-1-zhichaox.zeng@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org |
Series |
net/iavf: support Tx LLDP on scalar and AVX512
|
|
Message
Zhichao Zeng
Dec. 14, 2023, 6:58 a.m. UTC
This patch set adds an IAVF testpmd command "set tx lldp on|off" which will register an mbuf dynflag IAVF_TX_LLDP_DYNFLAG at the application level, currently only supported turning on. IAVF will fill the SWTCH_UPLINK bit in the Tx context descriptor based on the mbuf dynflag to send the LLDP packet. For avx512, need to close the Tx port first, then "set tx lldp on", and reopen the port to select correct Tx path. --- v2: split into patch set, refine commit log Zhichao Zeng (3): net/iavf: support Tx LLDP on scalar net/iavf: support Tx LLDP on AVX512 net/iavf: add Tx LLDP command doc/guides/rel_notes/release_24_03.rst | 3 ++ drivers/net/iavf/iavf_rxtx.c | 10 ++++ drivers/net/iavf/iavf_rxtx.h | 3 ++ drivers/net/iavf/iavf_rxtx_vec_avx512.c | 17 +++++++ drivers/net/iavf/iavf_rxtx_vec_common.h | 6 +++ drivers/net/iavf/iavf_testpmd.c | 68 +++++++++++++++++++++++++ drivers/net/iavf/meson.build | 3 ++ drivers/net/iavf/rte_pmd_iavf.h | 2 + 8 files changed, 112 insertions(+) create mode 100644 drivers/net/iavf/iavf_testpmd.c