diff options
| author |   Ido Schimmel <idosch@mellanox.com> | 2018-10-17 08:53:03 +0000 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2018-10-17 17:45:07 -0700 |
| commit | d3d19d4b8ca2efbcf4fc543ef5d2367999a89862 (patch) | |
| tree | ed18a801aa3fb92bcb2c0d5690340b6ecff1eb9b /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | tcp, ulp: remove socket lock assertion on ULP cleanup (diff) | |
| download | wireguard-linux-d3d19d4b8ca2efbcf4fc543ef5d2367999a89862.tar.xz wireguard-linux-d3d19d4b8ca2efbcf4fc543ef5d2367999a89862.zip | |
mlxsw: spectrum_fid: Allow setting and clearing NVE properties on FID
In the device, the VNI and the list of remote VTEPs a packet should be
flooded to is a property of the filtering identifier (FID).
During encapsulation, the VNI is taken from the FID the packet was
classified to. During decapsulation, the overlay packet is injected into
a bridge and classified to a FID based on the VNI it came with.
Allow NVE configuration for a FID. Currently, this is only supported
with 802.1D FIDs which are used for VLAN-unaware bridges. However, NVE
configuration is going to be supported with 802.1Q FIDs which is why the
related fields are placed in the common FID struct.
Since the device requires a 1:1 mapping between FID and VNI, the driver
maintains a hashtable keyed by VNI and checks if the VNI is already
associated with an existing FID.
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Reviewed-by: Petr Machata <petrm@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions