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 EE089A00BE; Thu, 28 May 2020 11:13:48 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0091C1D625; Thu, 28 May 2020 11:13:48 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id 8F2D91D540 for ; Thu, 28 May 2020 11:13:46 +0200 (CEST) IronPort-SDR: 2tLKP05eVvPR/y4oK2mJIJeNR/QRDlRqSgTDqXNfjhmbOUiDaxGMwTVkf6dL0hPnxGx6mWajz2 r57Pc7InTEZw== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 May 2020 02:13:45 -0700 IronPort-SDR: Ak+FosFWoYqum8wlfW/nJUaEbIi8Jp7YzAJ6mBVSLMntuj/JZ6z/qVL3YcUtVztwVXak7o9e/z Kt0a13jchuhg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,444,1583222400"; d="scan'208";a="285106500" Received: from silpixa00399498.ir.intel.com (HELO silpixa00399498.ger.corp.intel.com) ([10.237.222.52]) by orsmga002.jf.intel.com with ESMTP; 28 May 2020 02:13:44 -0700 From: Anatoly Burakov To: dev@dpdk.org Cc: david.hunt@intel.com, liang.j.ma@intel.com, reshma.pattan@intel.com Date: Thu, 28 May 2020 10:13:48 +0100 Message-Id: X-Mailer: git-send-email 2.17.1 Subject: [dpdk-dev] [PATCH 0/3] Add interrupt-only mode to l3fwd-power 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 20.05, l3fwd-power has become much more stringent about whether it allows initialization without initializing the librte_power library with it. This means that while previously the app could have been used to test RX interrupts functionality even if the app itself was in a half-working state, it is now no longer possible to do so. To address this use case, we're adding an interrupt-only mode that does not rely on librte_power or telemetry. This enables using l3fwd-power in environments where librte_power is not expected to work (such as inside a VM or on non-IA architectures). The RX/TX path is basically copy paste from legacy RX/TX path but with librte_power bits taken out. There seem to be two opposing schools of thought on whether we should have more or less examples. This patchset goes in the "less" direction where we add a new mode to an existing app, rather than creating a new one like it could be argued it deserves. Anatoly Burakov (3): l3fwd-power: disable interrupts by default l3fwd-power: only allow supported power library envs l3fwd-power: add interrupt-only mode examples/l3fwd-power/main.c | 234 +++++++++++++++++++++++++++++++++--- 1 file changed, 217 insertions(+), 17 deletions(-) -- 2.17.1