History log of /dpdk/drivers/net/mlx5/hws/mlx5dr_table.c (Results 1 – 11 of 11)
Revision Date Author Comments
# 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 ...


# 4711950b 06-May-2024 Itamar Gozlan <igozlan@nvidia.com>

net/mlx5/hws: set default miss when replacing table

Allowing the replacement of a miss table without enforcing
a previous disconnecting. This feature extension allows the
user to change the destinat

net/mlx5/hws: set default miss when replacing table

Allowing the replacement of a miss table without enforcing
a previous disconnecting. This feature extension allows the
user to change the destination miss table when the system
runs without losing traffic.

Fixes: b81f95ca770d ("net/mlx5/hws: support default miss table")
Cc: stable@dpdk.org

Signed-off-by: Itamar Gozlan <igozlan@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>

show more ...


# eefaf43d 26-Oct-2023 Shun Hao <shunh@nvidia.com>

net/mlx5/hws: support mirroring

This patch supports mirroring by adding an dest_array action. The action
accecpts a list containing multiple destination actions, and can duplicate
packet and forward

net/mlx5/hws: support mirroring

This patch supports mirroring by adding an dest_array action. The action
accecpts a list containing multiple destination actions, and can duplicate
packet and forward to each destination in the list.

Signed-off-by: Shun Hao <shunh@nvidia.com>
Acked-by: Alex Vesker <valex@nvidia.com>
Acked-by: Suanming Mou <suanmingm@nvidia.com>

show more ...


# 4baa7468 26-Oct-2023 Hamdan Igbaria <hamdani@nvidia.com>

net/mlx5/hws: add DevX object to Direct Rules action

Add mlx5dr_devx_obj struct to mlx5dr_action, so we could hold
the FT obj in dest table action.

Signed-off-by: Hamdan Igbaria <hamdani@nvidia.com

net/mlx5/hws: add DevX object to Direct Rules action

Add mlx5dr_devx_obj struct to mlx5dr_action, so we could hold
the FT obj in dest table action.

Signed-off-by: Hamdan Igbaria <hamdani@nvidia.com>
Acked-by: Suanming Mou <suanmingm@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 ...


# 54225e70 04-Jul-2023 Alex Vesker <valex@nvidia.com>

net/mlx5/hws: support default miss action on FDB

Add the support for default miss on HWS FDB, this implementation
was missing until now. Default miss can be used for more efficient
miss flow instead

net/mlx5/hws: support default miss action on FDB

Add the support for default miss on HWS FDB, this implementation
was missing until now. Default miss can be used for more efficient
miss flow instead of going to an empty matcher or some defecated
empty table.

Signed-off-by: Alex Vesker <valex@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>

show more ...


# e1df1578 20-Mar-2023 Hamdan Igbaria <hamdani@nvidia.com>

net/mlx5/hws: enhance forward table and FTE creation

Changed FW FT and FTE creation to allow dynamic creation.
Till now only FTE with vport destination action was supported.
Also enhanced forward ta

net/mlx5/hws: enhance forward table and FTE creation

Changed FW FT and FTE creation to allow dynamic creation.
Till now only FTE with vport destination action was supported.
Also enhanced forward table creation to be generic.

Signed-off-by: Hamdan Igbaria <hamdani@nvidia.com>
Reviewed-by: Alex Vesker <valex@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>

show more ...


# a5b44bc2 22-Mar-2023 Erez Shitrit <erezsh@nvidia.com>

net/mlx5/hws: fix shared context to use local defaults

Every Flow-table has a default miss behavior, meaning what action
to do in case of miss in that Flow-table.
When we are using shared Flow-table

net/mlx5/hws: fix shared context to use local defaults

Every Flow-table has a default miss behavior, meaning what action
to do in case of miss in that Flow-table.
When we are using shared Flow-table we should not use the shared
default instead we should use the default of the local Flow-table
that pointed by the shared Flow-table.

There are two cases that need to be fixed:
When the table created, the default miss should go to the alias ft
that will direct it back to local context.

And also when the rule is without specific hit address and we are
in a shared RTC from here it should be redirected back to the local
context.

Fixes: ce946c7d3999 ("net/mlx5/hws: support ibv context shared with local one")
Cc: stable@dpdk.org

Signed-off-by: Erez Shitrit <erezsh@nvidia.com>
Reviewed-by: Alex Vesker <valex@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 ...


# 01895651 09-Nov-2022 Erez Shitrit <erezsh@nvidia.com>

net/mlx5/hws: fix order of destroying default tables

This patch fixes the order dereferencing default FDB miss table and
destroying the flow table object. Flow table should be destroyed
before the d

net/mlx5/hws: fix order of destroying default tables

This patch fixes the order dereferencing default FDB miss table and
destroying the flow table object. Flow table should be destroyed
before the dereference.

Fixes: 394cc7ba4033 ("net/mlx5/hws: add table object")

Signed-off-by: Erez Shitrit <erezsh@nvidia.com>
Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Reviewed-by: Alex Vesker <valex@nvidia.com>
Acked-by: Matan Azrad <matan@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 ...