Re: [dpdk-dev] [PATCH v2] net/mlx5: enlarge maximal flow priority value

[Raslan Darawsheh <rasland@nvidia.com>]

Hi,

> -----Original Message-----
> From: Dong Zhou <dongzhou@nvidia.com>
> Sent: Tuesday, January 12, 2021 8:40 AM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v2] net/mlx5: enlarge maximal flow priority value
> 
> Currently, the maximal flow priority in non-root table to user
> is 4, it's not enough for user to do some flow match by priority,
> such as LPM, for one IPV4 address, we need 32 priorities for each
> bit of 32 mask length.
> 
> PMD will manage 3 sub-priorities per user priority according to L2,
> L3 and L4. The internal priority is 16 bits, user can use priorities
> from 0 - 21843.
> 
> Those enlarged flow priorities are only used for ingress or egress
> flow groups greater than 0 and for any transfer flow group.
> 
> Signed-off-by: Dong Zhou <dongzhou@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
> v2:
> * fix coding style issues, 'prority' to 'priority'.
> ---
Patch rebased and applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh