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 114B4A0524; Tue, 13 Apr 2021 20:39:45 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CCC2F161266; Tue, 13 Apr 2021 20:39:44 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id 8A05A161262 for ; Tue, 13 Apr 2021 20:39:42 +0200 (CEST) IronPort-SDR: q73KrI+idmsKph/St+7ByWjcVIFO2Tm5byOTBn1f78rtjqv94dveittEj2JCXpNVVc0Z4my+op 7nXscWvx3P6g== X-IronPort-AV: E=McAfee;i="6200,9189,9953"; a="181990381" X-IronPort-AV: E=Sophos;i="5.82,220,1613462400"; d="scan'208";a="181990381" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Apr 2021 11:39:35 -0700 IronPort-SDR: +xAXXnrGswrEx3KGO/moqToz0EjU6IysA0Kia1LJ388z5U8Py8u8zaBHkwEcZB2CXnGNdWsLE+ dZVnszaHk3ZQ== X-IronPort-AV: E=Sophos;i="5.82,220,1613462400"; d="scan'208";a="424371481" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.204.251]) ([10.213.204.251]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Apr 2021 11:39:28 -0700 To: Li Zhang , dekelp@nvidia.com, orika@nvidia.com, viacheslavo@nvidia.com, matan@nvidia.com, shahafs@nvidia.com, cristian.dumitrescu@intel.com, lironh@marvell.com, jerinj@marvell.com, ajit.khaparde@broadcom.com Cc: dev@dpdk.org, thomas@monjalon.net, rasland@nvidia.com, roniba@nvidia.com References: <20210331085405.1445546-1-lizh@nvidia.com> <20210413155958.2024584-1-lizh@nvidia.com> From: Ferruh Yigit X-User: ferruhy Message-ID: <49f1844e-1a27-0fc2-2eb9-12bf53452ede@intel.com> Date: Tue, 13 Apr 2021 19:39:23 +0100 MIME-Version: 1.0 In-Reply-To: <20210413155958.2024584-1-lizh@nvidia.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v5 0/4] Support PPS(packet per second) on meter 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" On 4/13/2021 4:59 PM, Li Zhang wrote: > Currently meter algorithms only supports rate is bytes per second(BPS). > Add packet_mode flag in meter profile parameters data structure. > So that it can meter traffic by packet per second. > > When packet_mode is 0, the profile rates and bucket sizes are > specified in bytes per second and bytes > when packet_mode is not 0, the profile rates and bucket sizes are > specified in packets and packets per second. > > Add the necessary checks to the existing drivers implementing > the rte_mtr API to makes sure that profiles with > packet_mode set to TRUE are rejected. > > RFC ("adds support PPS(packet per second) on meter") > https://patchwork.dpdk.org/project/dpdk/patch/20210125012023.1769769-2-lizh@nvidia.com/ > > V2: create a unified patch that contains both the series with > the API changes and the series with the necessary error checks in the drivers. > V3: Fix comments about commit-log. > V4: Fix comments about Depends-on and rebase. > V5: Fix comments about Depends-on and add acked. > > Li Zhang (4): > ethdev: add packet mode in meter profile structure > app/testpmd: add meter profile packet mode option > net/softnic: check meter packet mode > net/mvpp2: check meter packet mode > Series applied to dpdk-next-net/main, thanks.