| #
486f9aac |
| 24-Oct-2024 |
Hamdan Igbaria <hamdani@nvidia.com> |
net/mlx5/hws: introduce STE array matcher
introduce STE array matcher, where this matcher can only
be isolated under a parent table and not chained to the
table matchers chain.
Signed-off-by: Hamda
net/mlx5/hws: introduce STE array matcher
introduce STE array matcher, where this matcher can only
be isolated under a parent table and not chained to the
table matchers chain.
Signed-off-by: Hamdan Igbaria <hamdani@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
show more ...
|
| #
b81f95ca |
| 18-Sep-2023 |
Itamar Gozlan <igozlan@nvidia.com> |
net/mlx5/hws: support default miss table
A default miss table is a way to define what happens to traffic that does
not match any rule in a specific table. In hws, this is done by connecting
the sour
net/mlx5/hws: support default miss table
A default miss table is a way to define what happens to traffic that does
not match any rule in a specific table. In hws, this is done by connecting
the source table to the target table using the RTC.
This ensures that traffic that does not match any rule in the source table
is forwarded to the target table.
Signed-off-by: Itamar Gozlan <igozlan@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
show more ...
|
| #
ce946c7d |
| 05-Jan-2023 |
Erez Shitrit <erezsh@nvidia.com> |
net/mlx5/hws: support ibv context shared with local one
The idea is to have a shared ibv_context that all the resources
allocated on it (FT + TIR are exceptions)
Whenever a resource is created local
net/mlx5/hws: support ibv context shared with local one
The idea is to have a shared ibv_context that all the resources
allocated on it (FT + TIR are exceptions)
Whenever a resource is created locally an alias object to that resource
allocated and used in the other context.
The connections between the resources are done according to each type of
the resource, to the original resource, or its alias resource.
Signed-off-by: Erez Shitrit <erezsh@nvidia.com>
Reviewed-by: Alex Vesker <valex@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
show more ...
|
| #
394cc7ba |
| 20-Oct-2022 |
Alex Vesker <valex@nvidia.com> |
net/mlx5/hws: add table object
HWS table resides under the context object, each context can
have multiple tables with different steering types RX/TX/FDB.
The table is not only a logical object but
net/mlx5/hws: add table object
HWS table resides under the context object, each context can
have multiple tables with different steering types RX/TX/FDB.
The table is not only a logical object but it is also represented
in the HW, packets can be steered to the table, and from there
to other tables.
Signed-off-by: Erez Shitrit <erezsh@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
show more ...
|