From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8BE90A0471 for ; Mon, 12 Aug 2019 16:20:14 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 41098378B; Mon, 12 Aug 2019 16:20:13 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 36ED727D for ; Mon, 12 Aug 2019 16:20:11 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Aug 2019 07:20:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,377,1559545200"; d="scan'208";a="327368410" Received: from npg-dpdk-haiyue-1.sh.intel.com ([10.67.111.73]) by orsmga004.jf.intel.com with ESMTP; 12 Aug 2019 07:20:09 -0700 From: Haiyue Wang To: dev@dpdk.org Cc: Haiyue Wang Date: Mon, 12 Aug 2019 22:15:02 +0800 Message-Id: <1565619305-17116-1-git-send-email-haiyue.wang@intel.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Since some PMDs have multi-path for Rx/Tx, FD.io VPP will tell you in the Debug CLI what rx/tx function is being used: #show hardware-interface tx burst function: ice_xmit_pkts rx burst function: ice_recv_scattered_pkts But if the tx/rx is static, then 'dladdr' will return nil: tx burst function: (nil) │······················ rx burst function: (nil) │······················ For making things consistent and gracefull, we introduce an new string field to describe the Rx/Tx burst information. This is vendor-neutral, it is used to identify the Rx/Tx burst selection if the PMD has more than one. If a PMD supports this, then rxqinfo/txqinfo->burst_info[0] != '\0'. This is for net/ice PMD result. testpmd> show rxq info 0 0 ********************* Infos for port 0 , RX queue 0 ********************* Mempool: mbuf_pool_socket_0 RX prefetch threshold: 0 RX host threshold: 0 RX writeback threshold: 0 RX free threshold: 32 RX drop packets: off RX deferred start: off RX scattered packets: on Number of RXDs: 1024 Burst description: AVX2 Vector Scattered Rx <------------ NEW testpmd> show txq info 0 0 ********************* Infos for port 0 , TX queue 0 ********************* TX prefetch threshold: 32 TX host threshold: 0 TX writeback threshold: 0 TX RS threshold: 32 TX free threshold: 32 TX deferred start: off Number of TXDs: 1024 Burst description: AVX2 Vector Tx <------------ NEW Haiyue Wang (3): ethdev: add the Rx/Tx burst description field in queue information testpmd: show the Rx/Tx burst description field in queue net/ice: support the Rx/Tx burst description field in queue information app/test-pmd/config.c | 2 ++ drivers/net/ice/ice_rxtx.c | 49 ++++++++++++++++++++++++++++++++++++++++++ lib/librte_ethdev/rte_ethdev.h | 7 ++++++ 3 files changed, 58 insertions(+) -- 2.7.4