path: root/doc/guides/nics/mlx5.rst
diff options
authorNĂ©lio Laranjeiro <>2018-04-05 17:07:19 +0200
committerFerruh Yigit <>2018-04-14 00:41:44 +0200
commitccdcba53a3f4d12583c4378e7d8b702ce91e0499 (patch)
tree662bc815df87fc5f15a8f64c2ff1708294ca7625 /doc/guides/nics/mlx5.rst
parenta7082768655a16294a78b68be97e6997be59d778 (diff)
net/mlx5: use Netlink to add/remove MAC addresses
VF devices are not able to receive traffic unless it fully requests it though Netlink. This will cause the request to be processed by the PF which will add/remove the MAC address to the VF table if the VF is trusted. Signed-off-by: Nelio Laranjeiro <> Acked-by: Adrien Mazarguil <>
Diffstat (limited to 'doc/guides/nics/mlx5.rst')
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index ff02e86..72dee99 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -109,6 +109,15 @@ Limitations
- Flows with a VXLAN Network Identifier equal (or ends to be equal)
to 0 are not supported.
- VXLAN TSO and checksum offloads are not supported on VM.
+- VF: flow rules created on VF devices can only match traffic targeted at the
+ configured MAC addresses (see ``rte_eth_dev_mac_addr_add()``).
+.. note::
+ MAC addresses not already present in the bridge table of the associated
+ kernel network device will be added and cleaned up by the PMD when closing
+ the device. In case of ungraceful program termination, some entries may
+ remain present and should be removed manually by other means.