> -----Original Message-----
> From: Ian Stokes <[email protected]>
> Sent: Tuesday, February 12, 2019 7:17 PM
> To: Ilya Maximets <[email protected]>; Ophir Munk
> <[email protected]>; [email protected]
> Cc: Olga Shern <[email protected]>; Kevin Traynor
> <[email protected]>; Asaf Penso <[email protected]>; Thomas
> Monjalon <[email protected]>
> Subject: Re: [PATCH v1] doc: Add "Representors" topic document
>
> On 2/12/2019 1:15 PM, Ilya Maximets wrote:
> > On 11.02.2019 3:01, Ophir Munk wrote:
> >> This details how to configure representors ports.
> >>
> >> Signed-off-by: Ophir Munk <[email protected]>
> >> ---
> >> Documentation/topics/dpdk/phy.rst | 80
> +++++++++++++++++++++++++++++++++++++++
> >> 1 file changed, 80 insertions(+)
> >>
> >> diff --git a/Documentation/topics/dpdk/phy.rst
> >> b/Documentation/topics/dpdk/phy.rst
> >> index 1470623..3792fde 100644
> >> --- a/Documentation/topics/dpdk/phy.rst
> >> +++ b/Documentation/topics/dpdk/phy.rst
> >> @@ -219,6 +219,86 @@ For more information please refer to the `DPDK
> Port Hotplug Framework`__.
> >>
...
> >> +
> >> +Representors
> >> +------------
.....
> >> +This syntax shows that a representor is an enumerated eth device
> >> +(with a representor ID) which uses the PF PCI address.
> >> +The following commands add representors 3 and 5 using PCI device
> >> +address
> >> +``0000:08:00.0``::
> >> +
> >> + $ ovs-vsctl add-port br0 dpdk-rep3 -- set Interface dpdk-rep3
> type=dpdk \
> >> + options:dpdk-devargs=0000:08:00.0,representor=[3]
> >> +
> >> + $ ovs-vsctl add-port br0 dpdk-rep5 -- set Interface dpdk-rep5
> type=dpdk \
> >> + options:dpdk-devargs=0000:08:00.0,representor=[5]
> >> +
> >> +.. important::
> >> +
> >> + Representors ports are configured prior to OVS invocation and
> independently
> >> + of it, or by other means as well. Please consult a NIC vendor
> instructions
> >> + on how to establish representors.
> >
> > It'll be good to have configuration example for at least one commonly
> > used NIC (ixgbe/i40e ?). Or maybe a link to the docs where the process
> described.
> >
> > What do you think ?
> > Ian, maybe you could add some example, since you have already tried it in
> practice?
> >
>
> Good call, I'll draw up an incremental and post here, if acceptable we can
> roll
> it into the same patch.
>
In addition to Ian drawing - please find a link which details how to create VFs
for ConnectX-4 5 or 6 NICs:
https://docs.openstack.org/neutron/rocky/admin/config-ovs-offload.html section
"Create Compute virtual functions".
I will send an updated v2 with this reference.
> Ian
> >> To verify their correct configuration,
> >> + execute::
> >> +
> >> + $ ovs-vsctl show
> >> +
> >> + and make sure no errors are indicated.
> >> +
> >> +.. _multi-dev-configuration:
> >> +
> >> +
> >> +Port representors are an example of multi devices. There are NICs
> >> +which support multi devices by other methods than representors for
> >> +which a generic devargs syntax is used. The generic syntax is based on
> the device mac address::
> >> +
> >> + class=eth,mac=<MAC address>
> >> +
> >> +For example, the following command adds a port to a bridge called
> >> +``br0`` using an eth device whose mac address is ``00:11:22:33:44:55``::
> >> +
> >> + $ ovs-vsctl add-port br0 dpdk-mac -- set Interface dpdk-mac
> type=dpdk \
> >> + options:dpdk-devargs="class=eth,mac=00:11:22:33:44:55"
> >> +
> >> Jumbo Frames
> >> ------------
> >>
> >>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
