From patchwork Fri Apr 30 21:37:46 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Kathleen Capella X-Patchwork-Id: 92583 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 0CAA2A0546; Fri, 30 Apr 2021 23:38:03 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C49344014F; Fri, 30 Apr 2021 23:38:02 +0200 (CEST) Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by mails.dpdk.org (Postfix) with ESMTP id 88C0E4013F for ; Fri, 30 Apr 2021 23:38:01 +0200 (CEST) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id D15B61063; Fri, 30 Apr 2021 14:38:00 -0700 (PDT) Received: from 2p2660v4-1.austin.arm.com (2p2660v4-1.austin.arm.com [10.118.13.211]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C72123F73B; Fri, 30 Apr 2021 14:38:00 -0700 (PDT) From: Kathleen Capella To: Cc: dev@dpdk.org, nd@arm.com, Kathleen.Capella@arm.com, honnappa.nagarahalli@arm.com, dharmik.thakkar@arm.com, Kathleen Capella Date: Fri, 30 Apr 2021 16:37:46 -0500 Message-Id: <20210430213747.41530-1-kathleen.capella@arm.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Subject: [dpdk-dev] [RFC 0/1] app/testpmd: add l3fwd mode to testpmd 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 Sender: "dev" Performance of the LPM mode in L3fwd example application is used as an industry standard to compare between various platforms. Unfortunately, L3fwd example application lacks debugging capabilities to understand the performance bottlenecks and fix them. While debugging performance issues we need all the flexibility possible. Some of the capabilities we have used are: 1) ability to print hardware and software statistics - xstats, stats at port/queue level, burst stats to identify any headroom available, CPU cycles/packet etc 2) ability to modify all possible configurable parameters for the PMD as well as the application at run time without recompiling the code. Some of the parameters we have used are RX/TX queue depths, burst size, number of receive queues, PMD specific parameters etc. This configurability at runtime helps to understand and debug L3fwd performance issues quickly and effectively. It is possible to add all these capabilities to L3fwd example application. However, doing that we will result in L3fwd example application losing its purpose (of being a sample application). At the same time, testpmd application has all these capabilities to debug an application. In my opinion it makes sense to add L3fwd mode to testpmd. This patch adds l3fwd mode into testpmd to take advantage of the existing infrastructure in testpmd. I'd like to hear from the community if the structure of this change makes sense, namely, adding l3fwd as a separate fwd_engine into testpmd. This feature is not yet implemeted for SSE or AltiVec. Kathleen Capella (1): app/testpmd: add l3fwd mode to testpmd app/test-pmd/config.c | 66 +++++++ app/test-pmd/l3fwd.c | 356 ++++++++++++++++++++++++++++++++++ app/test-pmd/l3fwd.h | 143 ++++++++++++++ app/test-pmd/l3fwd_common.h | 268 +++++++++++++++++++++++++ app/test-pmd/l3fwd_lpm.h | 107 ++++++++++ app/test-pmd/l3fwd_lpm_neon.h | 169 ++++++++++++++++ app/test-pmd/l3fwd_neon.h | 234 ++++++++++++++++++++++ app/test-pmd/meson.build | 3 +- app/test-pmd/testpmd.c | 4 +- app/test-pmd/testpmd.h | 20 ++ 10 files changed, 1368 insertions(+), 2 deletions(-) create mode 100644 app/test-pmd/l3fwd.c create mode 100644 app/test-pmd/l3fwd.h create mode 100644 app/test-pmd/l3fwd_common.h create mode 100644 app/test-pmd/l3fwd_lpm.h create mode 100644 app/test-pmd/l3fwd_lpm_neon.h create mode 100644 app/test-pmd/l3fwd_neon.h