From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
by inbox.dpdk.org (Postfix) with ESMTP id 47FF1A0547;
Wed, 21 Apr 2021 12:23:34 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id B509B419EC;
Wed, 21 Apr 2021 12:23:33 +0200 (CEST)
Received: from mga17.intel.com (mga17.intel.com [192.55.52.151])
by mails.dpdk.org (Postfix) with ESMTP id 1715D419D3
for <dev@dpdk.org>; Wed, 21 Apr 2021 12:23:31 +0200 (CEST)
IronPort-SDR: e3olWqihCdp1kBHHEqcKVognGc//8Yj2dePp3BKtdnrMuSMa+7UregJd8awcYrWirWTq967V+P
og5l/ci0RGKw==
X-IronPort-AV: E=McAfee;i="6200,9189,9960"; a="175782115"
X-IronPort-AV: E=Sophos;i="5.82,238,1613462400"; d="scan'208";a="175782115"
Received: from fmsmga002.fm.intel.com ([10.253.24.26])
by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
21 Apr 2021 03:23:31 -0700
IronPort-SDR: 9UgqJTZHa+t5YLXJlt6iLhTl6YmgOzlJlhTHfWBUIM2yDmXIwzvChu6NQKkeUCtBQAIfeQpI6n
yK2u/NjUBQ+w==
X-IronPort-AV: E=Sophos;i="5.82,238,1613462400"; d="scan'208";a="455289319"
Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.206.218])
([10.213.206.218])
by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
21 Apr 2021 03:23:29 -0700
To: Jiawei Wang <jiaweiw@nvidia.com>, matan@nvidia.com, orika@nvidia.com,
viacheslavo@nvidia.com, shahafs@nvidia.com
Cc: dev@dpdk.org, thomas@monjalon.net, rasland@nvidia.com, roniba@nvidia.com,
asafp@nvidia.com
References: <1618848506-37569-1-git-send-email-jiaweiw@nvidia.com>
<1618927490-229267-1-git-send-email-jiaweiw@nvidia.com>
From: Ferruh Yigit <ferruh.yigit@intel.com>
X-User: ferruhy
Message-ID: <009a8230-ee63-a1a7-0fdc-0149a3e08e05@intel.com>
Date: Wed, 21 Apr 2021 11:23:25 +0100
MIME-Version: 1.0
In-Reply-To: <1618927490-229267-1-git-send-email-jiaweiw@nvidia.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] [PATCH v10 0/2] Support meter policy API
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
<mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
<mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>
On 4/20/2021 3:04 PM, Jiawei Wang wrote:
> Currently, the flow meter policy does not support multiple actions
> per color; also the allowed action types per color are very limited.
> In addition, the policy cannot be pre-defined.
>
> Due to the growing in flow actions offload abilities there is a potential
> for the user to use variety of actions per color differently.
> This new meter policy API comes to allow this potential in the most ethdev
> common way using rte_flow action definition.
> A list of rte_flow actions will be provided by the user per color
> in order to create a meter policy.
> In addition, the API forces to pre-define the policy before
> the meters creation in order to allow sharing of single policy
> with multiple meters efficiently.
>
> meter_policy_id is added into struct rte_mtr_params.
> So that it can get the policy during the meters creation.
>
> Add two common policy template as macros in the header file,
>
> RFC ("ethdev: add pre-defined meter policy API")
> https://patchwork.dpdk.org/project/dpdk/patch/20210318085815.804896-1-lizh@nvidia.com/
>
> Depends-on: series=16520 ("Add ASO meter support in MLX5 PMD ")
> https://patchwork.dpdk.org/project/dpdk/list/?series=16520
>
> v10:
> * Rebase.
>
> v9:
> * Rebase.
> * Fix the comments for softnic driver.
>
> v8:
> * Fix rebase conflict issues and CI warning.
>
> v7:
> * Fix comments and place two common policy template as macros.
>
> v6:
> * Delete policy example.
>
> v5:
> * Fix comments about rte_mtr_meter_policy_add.
>
> v4:
> * Fix comments about Depends-on.
>
> v3:
> * Fix coding style issues.
>
> v2:
> * Delete default policy and change relation doc files.
>
> Haifei Luo (1):
> app/testpmd: support policy actions per color
>
> Li Zhang (1):
> ethdev: add pre-defined meter policy API
>
Series applied to dpdk-next-net/main, thanks.