diff options
| author | Maor Gottlieb <maorg@nvidia.com> | 2021-07-26 09:20:14 +0300 |
|---|---|---|
| committer | Saeed Mahameed <saeedm@nvidia.com> | 2021-07-28 02:10:01 +0300 |
| commit | 8b54874ef1617185048029a3083d510569e93751 (patch) | |
| tree | cbbb68a657f0dd9fc8a5cb0f96048c5ebf5bffca /scripts/gdb/linux | |
| parent | 8373cd38a8888549ace7c7617163a2e826970a92 (diff) | |
| download | linux-8b54874ef1617185048029a3083d510569e93751.tar.xz | |
net/mlx5: Fix flow table chaining
Fix a bug when flow table is created in priority that already
has other flow tables as shown in the below diagram.
If the new flow table (FT-B) has the lowest level in the priority,
we need to connect the flow tables from the previous priority (p0)
to this new table. In addition when this flow table is destroyed
(FT-B), we need to connect the flow tables from the previous
priority (p0) to the next level flow table (FT-C) in the same
priority of the destroyed table (if exists).
---------
|root_ns|
---------
|
--------------------------------
| | |
---------- ---------- ---------
|p(prio)-x| | p-y | | p-n |
---------- ---------- ---------
| |
---------------- ------------------
|ns(e.g bypass)| |ns(e.g. kernel) |
---------------- ------------------
| | |
------- ------ ----
| p0 | | p1 | |p2|
------- ------ ----
| | \
-------- ------- ------
| FT-A | |FT-B | |FT-C|
-------- ------- ------
Fixes: f90edfd279f3 ("net/mlx5_core: Connect flow tables")
Signed-off-by: Maor Gottlieb <maorg@nvidia.com>
Reviewed-by: Mark Bloch <mbloch@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'scripts/gdb/linux')
0 files changed, 0 insertions, 0 deletions