In a virtual environment, the network controller may have to configure
some SR-IOV VF parameters for security reasons.
When the PF (host port) is driven by DPDK (OVS-DPDK case),
we face two different cases:
- driver is bifurcated (Mellanox case),
so the VF can be configured via the kernel.
- driver is on top of UIO or VFIO, so DPDK API is required,
and PMD-specific APIs were used.
This new generic API will avoid vendors fragmentation.
Some PMD-specific API could migrate to this generic model.
As an example, the default MAC address configuration is demonstrated
for a VF mapped to mlx5 representor port.
As it breaks the ABI, I propose to merge this API in DPDK 19.11-rc2.
I am sorry I had not send a patch since proposing a RFC in August.
(I gave priority to the summit and the -rc1 release)
Thomas Monjalon (3):
ethdev: identify SR-IOV VF from host
ethdev: set VF MAC address from host
net/mlx5: set VF MAC address from host
drivers/net/mlx5/mlx5.c | 6 +++
drivers/net/mlx5/mlx5.h | 1 +
drivers/net/mlx5/mlx5_mac.c | 19 ++++++++
lib/librte_ethdev/rte_ethdev.c | 55 +++++++++++++++++++++---
lib/librte_ethdev/rte_ethdev.h | 38 ++++++++++++++++
lib/librte_ethdev/rte_ethdev_core.h | 1 +
lib/librte_ethdev/rte_ethdev_version.map | 1 +
7 files changed, 114 insertions(+), 7 deletions(-)
--
2.23.0
