Bring more flexibility and control over both flow rule insertion
and packet matching mechanisms. Introduce 2 new flow table types:
1. Allow a user to specify the insertion type used in template tables.
The insertion type is responsible for choosing the appropriate key
value used to map inserted fl
Allow user to specify insertion type used in template tables.
The insertion type is responsible for choosing the appropriate key
value used to map inserted flow rules into a template table.
Flow rules can be inserted by calculating the hash value for
the pattern or inserted by index via the new cr
Allow user to specify hash calculation function used in template tables.
The hash calculation type is responsible for the calculation of the flow
rule index a packet would hit upon arrival at the table.
Control over this is useful for applications with custom RSS algorithms,
for example. An applic
Add testpmd CLI interface for a template table hash function.
Available types are: default, linear, crc32 and crc16.
flow template_table 0 create table_id 0 hash_func linear ...
Signed-off-by: Alexander Kozyrev
---
app/test-pmd/cmdline_flow.c | 69 -
1 file ch
Add testpmd CLI interface for specifying a template table insertion type.
Available types are: pattern and index.
flow template_table 0 create table_id 0 insertion_type index ...
Allow specifying the rule index instead of the pattern template index:
flow queue 0 create 0 template_table 0 rule_index
Add the insertion type and hash calculation function of a template table.
Support the new rte_flow_async_create_by_index() Flow API to allow
flow rules insertion into a specified index of index-based template tables.
Set MLX5_LINEAR_HASH_TAG_INDEX as a special id for specifiyng the index.
Allow to
Pass the insertion type and hash calculation function of a table
to the mlx5 PMD driver. Create appropriate table as requested.
Note that 16-bit checksum hash calculation is not supported yet.
Signed-off-by: Alexander Kozyrev
---
drivers/net/mlx5/mlx5_flow_hw.c | 26 +-
1
New Flow API allows to insert flow rules into a specified
index for tables with the index-based insertion type.
Implement rte_flow_async_create_by_index API in mlx5 PMD.
Signed-off-by: Alexander Kozyrev
---
drivers/net/mlx5/mlx5_flow.c| 61 +
drivers/net/mlx5/mlx5_flow.h
Allow copy of the hash result via modify_field Flow API.
Setting this value is not allowed, it is read-only field.
Signed-off-by: Alexander Kozyrev
---
drivers/net/mlx5/mlx5_flow_dv.c | 12
drivers/net/mlx5/mlx5_flow_hw.c | 5 +++--
2 files changed, 15 insertions(+), 2 deletions(-)
Set MLX5_LINEAR_HASH_TAG_INDEX as a special id for the TAG item:
it holds the index in a linear table for a packet to land to.
This rule index in the table uses upper 16-bits of REG_C_3,
handle this TAG item in the modify_field API for setting the index.
Signed-off-by: Alexander Kozyrev
---
driv
There is a dump file with debug information created
for an error CQE to help with troubleshooting later.
It starts with the last CQE, which, presumably is the error CQE.
But this is only true for the scalar Rx burst routing since
we handle CQEs there one by one and detect the error immediately.
For
For non-fatal syndromes like LOCAL_LENGTH_ERR, the Rx queue reset
shouldn't be triggered. Rx queue could continue with the next packets
without any recovery. Only three syndromes warrant Rx queue reset:
LOCAL_QP_OP_ERR, LOCAL_PROT_ERR and WR_FLUSH_ERR.
Do not initiate a Rx queue reset in any other
The CQE opcode is never checked for a compressed CQE in
the vectorized Rx burst routines. It is assumed that
compressed CQEs are always valid and skipped error checking.
This is obviously not the case and error CQEs may be
compressed together as well. Need to check for the
MLX5_CQE_RESP_ERR opcode
On Fri, Jan 27, 2023 at 8:04 AM Shivah Shankar Shankar Narayan Rao
wrote:
>
> External Email
>
> --
> 25/01/2023 20:01, Jerin Jacob:
> > On Wed, Jan 25, 2023 at 7:50 PM Thomas Monjalon wrote:
> > > 14/11/2022 13:02, jer...@marvel
Please see inline.
> -Original Message-
> From: Thomas Monjalon
> Sent: Thursday, January 26, 2023 4:33 PM
> To: Nithin Kumar Dabilpuram
> Cc: Aman Singh ; Yuying Zhang
> ;
> Ivan Malov ; Andrew Rybchenko
> ; dev@dpdk.org; Hanumanth Reddy Pothula
> ; Ferruh Yigit ;
> viachesl...@nvidia
On Thu, Jan 26, 2023 at 8:43 PM Ori Kam wrote:
>
>
>
> > -Original Message-
> > From: Rakesh Kudurumalla
> > Sent: Wednesday, 18 January 2023 10:10
> >
> >
> > > -Original Message-
> > > From: Rakesh Kudurumalla
> > > Sent: Tuesday, January 10, 2023 12:12 PM
> > > To: Ori Kam ; Je
On Thu, Jan 26, 2023 at 4:27 PM Thomas Monjalon wrote:
>
> 25/01/2023 15:59, Srikanth Yalavarthi:
> > From: Thomas Monjalon
> > > 25/01/2023 14:25, Srikanth Yalavarthi:
> > > > From: Thomas Monjalon
> > > > > 20/12/2022 18:52, Srikanth Yalavarthi:
> > > > > > This patch series implements the com
101 - 117 of 117 matches
Mail list logo