[ovs-dev] [PATCH dpdk-latest v4] build: Add support for DPDK meson build.

[Pai G, Sunil]

<snipped>
> > I tried your build commands using latest dpdk-next-net and OVS-dpdk-
> latest branch. It worked fine for me on ubuntu18.04.
> > Moreover, GHA and travis CI's are passing for the shared builds.
> > So, it might be a problem with the system you are using.
> > Best to check the paths you are setting as well.
> >
> > Btw, which branch in OVS and which OS are you using ?
> > Could you also try running a sample application in dpdk like l2fwd and check
> if it works fine as well ?
> Yes, I use the dpdk helloworld to test.
> ./build/helloworld -n 4 -c 4 -a
> 0000:82:00.0,dv_flow_en=1,dv_esw_en=1,l3_vxlan_en=1,dv_xmeta_en=2,r
> epresentor=[0-2]
> EAL: Detected 56 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'VA'
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: 0000:82:00.0 (socket 1)
> common_mlx5: RTE_MEM is selected.
> mlx5_pci: Size 0xFFFF is not power of 2, will be aligned to 0x10000.
> EAL: No legacy callbacks, legacy socket not created hello from core 2
> 
> But there is error in ovs:
> $ ovs-vsctl show
> a360a9ac-d269-4e89-b01c-c09331b9fb00
>     Bridge br-int
>         datapath_type: netdev
>         Port tun
>             Interface tun
>                 type: vxlan
>                 options: {key=flow, local_ip="10.96.74.2", remote_ip=flow}
>         Port br-int
>             Interface br-int
>                 type: internal
>         Port rep1
>             Interface rep1
>                 type: dpdk
>                 options: {dpdk-devargs="0000:82:00.0,representor=[1]"}
>                 error: "Error attaching device '0000:82:00.0,representor=[1]' to DPDK"
> 
> 
> ovs-vswitchd log:
> 2020-12-15T21:20:41.703Z|00333|netdev|WARN|rep1: could not set
> configuration (Invalid argument) 2020-12-
> 15T21:20:41.703Z|00334|dpdk|ERR|Invalid port_id=256
> 2020-12-15T21:20:41.703Z|00335|dpdk|ERR|EAL: failed to parse device
> "0000:82:00.0"
> 2020-12-15T21:20:41.703Z|00336|dpdk|ERR|EAL: failed to parse device
> "0000:82:00.0"
> 2020-12-15T21:20:41.703Z|00337|dpdk|ERR|EAL: Failed to attach device on
> primary process 2020-12-
> 15T21:20:41.703Z|00338|netdev_dpdk|WARN|Error attaching device
> '0000:82:00.0,representor=[0]' to DPDK
> 
> One question, did you attach a dpdk port to ovs ?

Yes, I attached physical as well as virtual ports and both got added without err.

I suspect you might have to add a conf file pointing to the dpdk libraries , something like mentioned here:
https://www.cyberciti.biz/faq/linux-setting-changing-library-path/

Also, what does the ldd report for ovs-vswitchd binary ?



> 
> ovs commit-id:
> af06184705072804a4c1374f9c824c9e4c241c26
> dpdk-next-net
> d3fa7b89f0b893f051cb4cef1cbc961cb59f5721
> systeminfo
> CentOS Linux release 7.6.1810 (Core)
> kernel 3.10.0-957.1.3.el7.x86_64
> 
> >
> > >
<snipped>