Wednesday, March 21, 2018 3:40 PM, Nelio Laranjeiro: > All Netlink request the PMD will do can also be done by a iproute2 command > line interface, letting the operator configure the VF behavior without having > to modify the application nor reaching PMD limits (e.g. MAC address number > limit). > > Signed-off-by: Nelio Laranjeiro <nelio.laranje...@6wind.com> > Acked-by: Adrien Mazarguil <adrien.mazarg...@6wind.com> > --- > doc/guides/nics/mlx5.rst | 11 +++++++++++ drivers/net/mlx5/mlx5.c | 9 > ++++++++- drivers/net/mlx5/mlx5.h | 1 + > 3 files changed, 20 insertions(+), 1 deletion(-) > > diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index > 46d26e4c8..4c7bf1c56 100644 > --- a/doc/guides/nics/mlx5.rst > +++ b/doc/guides/nics/mlx5.rst > @@ -135,6 +135,8 @@ 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()``).
Should this comment be in the first patch of the series?
