> Dpdk port representors were introduced in dpdk versions 18.xx.
> Prior to port representors there was a one-to-one relationship between an
> rte device (e.g. PCI bus) and an eth device (referenced as dpdk port id in
> OVS). With port representors the relationship becomes one-to-many rte
> device to eth devices.
> For example in [3] there are two devices (representors) using the same PCI
> physical address 0000:08:00.0: "0000:08:00.0,representor=[3]" and
> "0000:08:00.0,representor=[5]".
> This commit handles the new one-to-many relationship. For example, when
> one of the device port representors in [3] is closed - the PCI bus cannot
> be detached until the other device port representor is closed as well. OVS
> remains backward compatible by supporting dpdk legacy PCI ports which do
> not include port representors.
> Dpdk port representors related commits are listed in [1]. Dpdk port
> representors documentation appears in [2]. A sample configuration which
> uses two representors ports (the output of "ovs-vsctl show"
> command) is shown in [3].
>
> [1]
> e0cb96204b71 ("net/i40e: add support for representor ports")
> cf80ba6e2038 ("net/ixgbe: add support for representor ports")
> 26c08b979d26 ("net/mlx5: add port representor awareness")
>
> [2]
> https://doc.dpdk.org/guides-18.11/prog_guide/switch_representation.html
>
> [3]
> Bridge "ovs_br0"
> Port "ovs_br0"
> Interface "ovs_br0"
> type: internal
> Port "port-rep3"
> Interface "port-rep3"
> type: dpdk
> options: {dpdk-devargs="0000:08:00.0,representor=[3]"}
> Port "port-rep5"
> Interface "port-rep5"
> type: dpdk
> options: {dpdk-devargs="0000:08:00.0,representor=[5]"}
> ovs_version: "2.10.90"
>
> Signed-off-by: Ophir Munk <[email protected]>
> Co-authored-by: Ilya Maximets <[email protected]>
> Signed-off-by: Ilya Maximets <[email protected]>
Thanks All for the work on this.
I've pushed this to master so it will be part of the 2.11 release.
It's understood that there is a follow on task to add documentation for this to
OVS in the coming weeks before the 2.11 release. New documentation will also be
added to DPDK that OVS will reference.
Thanks
Ian
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
