From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 62545A0501; Sat, 2 Apr 2022 13:03:41 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 19EC64067E; Sat, 2 Apr 2022 13:03:41 +0200 (CEST) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mails.dpdk.org (Postfix) with ESMTP id E34B140143 for ; Sat, 2 Apr 2022 13:03:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1648897420; x=1680433420; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=ErWyPWdT4L16VGveIAc8YaD22uzdZBW/Wzl29Spun/g=; b=F2Qt1wZInFSRyE9MhGC2GQJkZztm+y7yJbAizzIvHo5Vv0sdvbPSCJw8 kIfssaWmitEhUnpQt7szhKnV7DyWD9nRgzIDGnYeslzKasppFZaS3oBB5 DSijVsSZHVVFmdKozrJIkVHT9/i6tLILqRYUSE3gPrpm6vNPnneXspCdh PhJaTDSiVaMy0KK8wxLlvdAlWsTtTesF2/S3OrOZzs2611utHBiFW4j0e TTh2pFM0A4s/W/AZ4Np/HrF6se5iaocrNXjUIIDAca6slKHLkwPCyDbRJ EUe2f1e8v0ZBTaBQd1T7U6tUIIT1n7jZaWZLd4Rvh0qs4GxcvP3orNSSy w==; X-IronPort-AV: E=McAfee;i="6200,9189,10304"; a="247803592" X-IronPort-AV: E=Sophos;i="5.90,229,1643702400"; d="scan'208";a="247803592" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2022 04:03:38 -0700 X-IronPort-AV: E=Sophos;i="5.90,229,1643702400"; d="scan'208";a="568182918" Received: from unknown (HELO localhost.localdomain) ([10.239.251.3]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2022 04:03:34 -0700 From: wenxuanx.wu@intel.com To: thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru, xiaoyun.li@intel.com, aman.deep.singh@intel.com, yuying.zhang@intel.com, qi.z.zhang@intel.com Cc: dev@dpdk.org, stephen@networkplumber.org, mb@smartsharesystems.com, viacheslavo@nvidia.com, ping.yu@intel.com, Xuan Ding Subject: [v4 0/3] ethdev: introduce protocol type based header split Date: Sat, 2 Apr 2022 10:41:06 +0000 Message-Id: <20220402104109.472078-1-wenxuanx.wu@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220303060136.36427-1-xuan.ding@intel.com> References: <20220303060136.36427-1-xuan.ding@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org From: Xuan Ding Header split consists of splitting a received packet into two separate regions based on the packet content. It is useful in some scenarios, such as GPU acceleration. The splitting will help to enable true zero copy and hence improve the performance significantly. This patchset extends the current buffer split to support protocol based header split. When Rx queue is configured with header split feature, packets received will be directly splitted into two different mempools. v3->v4: * Use RTE_ETH_RX_HEADER_SPLIT_NONE instead of 0. v2->v3: * Fix a PMD bug. * Add rx queue header split check. * Revise the log and doc. v1->v2: * Add support for all header split protocol types. Xuan Ding (3): ethdev: introduce protocol type based header split app/testpmd: add header split configuration net/ice: support header split in Rx data path app/test-pmd/cmdline.c | 117 ++++++++++++++ app/test-pmd/testpmd.c | 6 +- app/test-pmd/testpmd.h | 2 + drivers/net/ice/ice_ethdev.c | 10 +- drivers/net/ice/ice_rxtx.c | 223 ++++++++++++++++++++++---- drivers/net/ice/ice_rxtx.h | 16 ++ drivers/net/ice/ice_rxtx_vec_common.h | 3 + lib/ethdev/rte_ethdev.c | 34 +++- lib/ethdev/rte_ethdev.h | 48 +++++- 9 files changed, 417 insertions(+), 42 deletions(-) -- 2.17.1