diff options
| author | Paul Blakey <[email protected]> | 2021-11-23 14:41:18 +0200 |
|---|---|---|
| committer | Saeed Mahameed <[email protected]> | 2022-03-10 23:38:23 -0800 |
| commit | 7690900052303e758b797db1ff8013fe425d1806 (patch) | |
| tree | 477b1fe97297ddedf512cfd80a252f2f1c6508a1 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | a3540effb766b868af429ae6f4909457b4d4f5ea (diff) | |
net/mlx5: CT: Introduce a platform for multiple flow steering providers
Currently, fs_core layer provides flow steering services to the driver
including: autogroups, allocating FTEs (flow table entries) and FTE ids,
and support of fte action modification. If then software steering is
configured, rule insertion will go through a translation layer from
firmware buffers to software steering objects (see fs_dr.c).
The connection tracking table is a system table that is not directly
controlled by the user and is a very high scale table. These fs_core
services introduces an overhead that may be optimized by using software
steering API directly.
Introduce ct flow steering interface to allow multiple flow steering
providers. Use the new interface to implement the current dmfs (device
managed flow steering) provider which uses fs_core insertion.
Signed-off-by: Paul Blakey <[email protected]>
Reviewed-by: Oz Shlomo <[email protected]>
Reviewed-by: Roi Dayan <[email protected]>
Signed-off-by: Saeed Mahameed <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions