> -----Original Message-----
> From: Ophir Munk <ophi...@nvidia.com>
> Sent: Tuesday, February 25, 2025 13:02
> To: Dariusz Sosnowski <dsosnow...@nvidia.com>; Slava Ovsiienko
> <viachesl...@nvidia.com>; Bing Zhao <bi...@nvidia.com>; Ori Kam
> <or...@nvidia.com>; Suanming Mou <suanmi...@nvidia.com>; Matan Azrad
> <ma...@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasl...@nvidia.com>
> Subject: [PATCH V1 2/4] net/mlx5: support FDB unified domain
>
> Legacy FDB domain is enhanced with optional three sub-domains: FDB_RX
> FDB_TX and FDB_UNIFIED. Based on FW capability bit mlx5 will work in either
> legacy or unified mode. To work in fdb unified mode the flow attribute
> transfer
> bit must be set and the fdb sub domains are determined by the table specialize
> flags SPECIALIZE_TRANSFER_WIRE_ORIG and
> SPECIALIZE_TRANSFER_VPORT_ORIG.
>
> +------------+-------------+--------------+
> | WIRE_ORIG | VPORT_ORIG | FDB domain |
> +------------+-------------+--------------+
> | 0 | 0 | FDB_UNIFIED |
> | 0 | 1 | FDB_TX |
> | 1 | 0 | FDB_RX |
> +------------+-------------+--------------+
>
> There can be no two groups which only differ in their fdb sub domain.
> A table must be created in a group which has the same fdb sub domain.
>
> Signed-off-by: Ophir Munk <ophi...@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnow...@nvidia.com>
Best regards,
Dariusz Sosnowski
