On Tue, Oct 23, 2018 at 11:53:30AM +0200, Andrzej Ostruszka wrote:
> Flavio
>
> Thank you again for trying to help me. Luckily I've solved the problem.
> So here I'll just document it for the benefit of other people with the
> same problem.
Hi Andrzej,
Glad to know that you solved the problem. I am not sure if you're
familiar with git and patch. If you are, perhaps this would be a
great opportunity for you to change the relevant documentation to
add your findings and send us a patch.
If you're not comfortable in doing it, I'd suggest to send a
documentation snippet, then we can try to integrate it.
Thanks,
fbl
>
> On 10/19/2018 08:12 PM, Flavio Leitner wrote:
> > On Mon, Oct 08, 2018 at 11:52:24AM +0200, Andrzej Ostruszka wrote:
> [...]
> >> ovs-vsctl: Error detected while setting up 'dpdk-p0': Error attaching
> >> device '08:00.0' to DPDK. See ovs-vswitchd log for details.
> >> ovs-vsctl: The default log directory is "/usr/local/var/log/openvswitch".
> >>
> >> and in there the confirmation from DPDK:
> >>
> >> 2018-10-08T09:38:28.234Z|00058|dpdk|ERR|EAL: Cannot find unplugged
> >> device (08:00.0)
> >> 2018-10-08T09:38:28.234Z|00059|netdev_dpdk|WARN|Error attaching device
> >> '08:00.0' to DPDK
> >> 2018-10-08T09:38:28.234Z|00060|netdev|WARN|dpdk-p0: could not set
> >> configuration (Invalid argument)
>
> The key word in the above log was "unplugged". What actually happened
> when I have given PCI address is that OvS tried to attach the driver
> when it already has been attached.
>
> So it looks like upon the startup OvS does a scan and attaches the ports
> (excerpt from the log):
> |INFO|EAL: PCI device 0000:01:00.0 on NUMA socket -1
> |WARN|EAL: Invalid NUMA socket, default to 0
> |INFO|EAL: probe driver: 15b3:1019 net_mlx5
> |INFO|PMD: net_mlx5: PCI information matches, using device "mlx5_0"
> (SR-IOV: false)
> |INFO|PMD: net_mlx5: 1 port(s) detected
>
> So I've taken a look at the code and saw that OvS takes the dpdk-devargs
> and first searches for the port by that name and if not found then it
> tries to attach/hotplug using this value. Thus the solution was to
> change the value of dpdk-devargs to the name of the port (mlx5_0 and
> mlx5_1) instead of PCI address. So with the following config everything
> works just fine - I guess the documentation could be updated a bit though.
>
> # ovs-vsctl show
> 67be421b-d397-4173-b1d5-e7d80f641daa
> Bridge "br0"
> Port "dpdk-p1"
> Interface "dpdk-p1"
> type: dpdk
> options: {dpdk-devargs="mlx5_1"}
> Port "br0"
> Interface "br0"
> type: internal
> Port "dpdk-p0"
> Interface "dpdk-p0"
> type: dpdk
> options: {dpdk-devargs="mlx5_0"}
> ovs_version: "2.10.90"
>
> Best regards
> Andrzej
> _______________________________________________
> discuss mailing list
> [email protected]
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
--
Flavio
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
