diff options
| author |   Amit Cohen <amcohen@nvidia.com> | 2022-06-23 10:17:35 +0300 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2022-06-24 12:32:33 +0100 |
| commit | 04e85970ceead5301337afd0d78012546494e0a1 (patch) | |
| tree | 943f0773449af1e9205efb1781b8a5765053cc2e /drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c | |
| parent | mlxsw: spectrum_fid: Pass FID structure to __mlxsw_sp_fid_port_vid_map() (diff) | |
| download | linux-dev-04e85970ceead5301337afd0d78012546494e0a1.tar.xz linux-dev-04e85970ceead5301337afd0d78012546494e0a1.zip | |
mlxsw: spectrum: Use different arrays of FID families per-ASIC type
Egress VID for layer 2 multicast is determined from two tables, the MPE
and PGT tables. The MPE table is a two dimensional table indexed by local
port and SMPE index, which should be thought of as a FID index.
In Spectrum-1 the SMPE index is derived from the PGT entry, whereas in
Spectrum-2 and newer ASICs the SMPE index is a FID attribute configured
via the SFMR register.
The validity of the SMPE index in SFMR is influenced from two factors:
1. FID family. SMPE index is reserved for rFIDs, as their flooding is
handled by firmware.
2. ASIC generation. SMPE index is always reserved for Spectrum-1.
As such, the validity of the SMPE index should be an attribute of the FID
family and have different arrays of FID families per-ASIC type.
As a preparation for SMPE index configuration, create separate arrays of
FID families for different ASICs.
Signed-off-by: Amit Cohen <amcohen@nvidia.com>
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c')
0 files changed, 0 insertions, 0 deletions