From: Raslan Darawsheh <rasland@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Michael Baum <michaelba@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
Jack Min <jackmin@nvidia.com>
Subject: RE: [PATCH v1] net/mlx5: disallow multiple ASO actions in a single flow
Date: Thu, 10 Mar 2022 09:21:14 +0000 [thread overview]
Message-ID: <BYAPR12MB30789E408BB571F03BB671F2CF0B9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220309120829.1485659-1-rongweil@nvidia.com>
Hi,
> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Wednesday, March 9, 2022 2:08 PM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-
> Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>; Michael Baum
> <michaelba@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>;
> stable@dpdk.org; Jack Min <jackmin@nvidia.com>
> Subject: [PATCH v1] net/mlx5: disallow multiple ASO actions in a single flow
>
> For now, only one ASO action is supported in a single flow.
> Flow with more than one ASO action should be rejected in the
> validation stage.
>
> Flow with action non-shared AGE and COUNT together should be
> treated as non-ASO because AGE will fall back to use HW counter,
> not ASO hit object.
>
> Group 0 will use HW counter for AGE action even if no COUNT action.
>
> This commit will reject patterns (no matter which group if transfer)
> like:
> 1. group 1 pattern... / end actions age / meter / end
> 2. group 1 pattern... / end actions conntrack / meter / end
> 3. group 1 pattern... / end actions age / conntrack... / end
>
> If AGE comes together with COUNT in the above patterns, it's allowed.
>
> Fixes: daed4b6e ("net/mlx5: use aging by counter when counter exists")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> Acked-by: Xiaoyu Min <jackmin@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-03-10 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:08 Rongwei Liu
2022-03-10 9:21 ` Raslan Darawsheh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BYAPR12MB30789E408BB571F03BB671F2CF0B9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=jackmin@nvidia.com \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).