Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
I'm not sure about that since as I mentioned before I haven't tried it before, so give it a try and let me know if it worked for you. Kindest regards, Raslan Darawsheh -Original Message- From: Tobias Urdin [mailto:tobias.ur...@crystone.com] Sent: Monday, June 11, 2018 3:14 PM To: Raslan Darawsheh Cc: users@dpdk.org Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch I found this librte-pmd-mlx4 driver but it's for 18.02 and I have dpdk 17.11.1 installed. It contains files: ./lib/x86_64-linux-gnu/dpdk-18.02-drivers/librte_pmd_mlx4.so.18.02 ./lib/x86_64-linux-gnu/librte_pmd_mlx4.so.18.02 I assume I can compile librte-pmd-mlx4 manually for 17.11 instead and place it in that folder. It looks like this: $ls -l /usr/lib/x86_64-linux-gnu/dpdk-17.11-drivers/ | head -n 5 total 0 lrwxrwxrwx 1 root root 35 Mar 22 10:23 librte_mempool_octeontx.so.17.11 -> ../librte_mempool_octeontx.so.17.11 lrwxrwxrwx 1 root root 31 Mar 22 10:23 librte_mempool_ring.so.17.11 -> ../librte_mempool_ring.so.17.11 lrwxrwxrwx 1 root root 32 Mar 22 10:23 librte_mempool_stack.so.17.11 -> ../librte_mempool_stack.so.17.11 lrwxrwxrwx 1 root root 32 Mar 22 10:23 librte_pmd_af_packet.so.17.11 -> ../librte_pmd_af_packet.so.17.11 ... Would that be enough or is there anything else I need? Best regards On 06/11/2018 02:07 PM, Raslan Darawsheh wrote: > I think OVS-DPDK has static linking for dpdk and I'm not sure you can > do it this way > > Kindest regards, > Raslan Darawsheh > > -Original Message- > From: Tobias Urdin [mailto:tobias.ur...@crystone.com] > Sent: Monday, June 11, 2018 3:05 PM > To: Raslan Darawsheh > Cc: users@dpdk.org > Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch > > Ok, I'm more wondering if there is any way I can build a librte-pmd-mlx4 > package that supplies the compiled PMD or something like that instead of > having to rebuild all the major parts? > > Thanks! > Best regards > > On 06/11/2018 01:51 PM, Raslan Darawsheh wrote: >> I think you can upgrade the current version that you have as seen in this >> article: >> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc >> s >> .openvswitch.org%2Fen%2Flatest%2Fintro%2Finstall%2Fgeneral%2F%23hot-u >> p >> grading=02%7C01%7Crasland%40mellanox.com%7Cfdaa105976c744dba2f90 >> 8 >> d5cf9394cc%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C1%7C6366431551416 >> 0 >> 5703=VhpqI3M4RdnD5Shpbt6O8YmufIKiyoYK9kxO9TR1Yrk%3D=0 >> >> but, I haven't tried it before. >> >> Kindest regards, >> Raslan Darawsheh >> >> -----Original Message----- >> From: Tobias Urdin [mailto:tobias.ur...@crystone.com] >> Sent: Monday, June 11, 2018 2:45 PM >> To: Raslan Darawsheh >> Cc: users@dpdk.org >> Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch >> >> Is there any to skip compiling DPDK and OVS+OVS-DPDK and instead use the >> ones I have installed? >> Only compiling the Mellanox PMD module/binary or something similar to that? >> >> I can see that other drivers supply pmd packages like below. >> >> $dpkg -l | grep -E "openvswitch|pmd|dpdk" >> ii dpdk >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (runtime) >> ii librte-pmd-af-packet17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-af-packet runtime library) >> ii librte-pmd-ark17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte_pmd_ark runtime library) >> ii librte-pmd-avp17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte_pmd_avp runtime library) >> ii librte-pmd-bnxt17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-bnxt runtime library) >> ii librte-pmd-bond17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-bond runtime library) ii >> librte-pmd-crypto-scheduler17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte_pmd_crypto_scheduler runtime library) >> ii librte-pmd-cxgbe17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-cxgbe runtime library) >> ii librte-pmd-e1000-17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librt
Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
I found this librte-pmd-mlx4 driver but it's for 18.02 and I have dpdk 17.11.1 installed. It contains files: ./lib/x86_64-linux-gnu/dpdk-18.02-drivers/librte_pmd_mlx4.so.18.02 ./lib/x86_64-linux-gnu/librte_pmd_mlx4.so.18.02 I assume I can compile librte-pmd-mlx4 manually for 17.11 instead and place it in that folder. It looks like this: $ls -l /usr/lib/x86_64-linux-gnu/dpdk-17.11-drivers/ | head -n 5 total 0 lrwxrwxrwx 1 root root 35 Mar 22 10:23 librte_mempool_octeontx.so.17.11 -> ../librte_mempool_octeontx.so.17.11 lrwxrwxrwx 1 root root 31 Mar 22 10:23 librte_mempool_ring.so.17.11 -> ../librte_mempool_ring.so.17.11 lrwxrwxrwx 1 root root 32 Mar 22 10:23 librte_mempool_stack.so.17.11 -> ../librte_mempool_stack.so.17.11 lrwxrwxrwx 1 root root 32 Mar 22 10:23 librte_pmd_af_packet.so.17.11 -> ../librte_pmd_af_packet.so.17.11 ... Would that be enough or is there anything else I need? Best regards On 06/11/2018 02:07 PM, Raslan Darawsheh wrote: > I think OVS-DPDK has static linking for dpdk and I'm not sure you can do it > this way > > Kindest regards, > Raslan Darawsheh > > -Original Message- > From: Tobias Urdin [mailto:tobias.ur...@crystone.com] > Sent: Monday, June 11, 2018 3:05 PM > To: Raslan Darawsheh > Cc: users@dpdk.org > Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch > > Ok, I'm more wondering if there is any way I can build a librte-pmd-mlx4 > package that supplies the compiled PMD or something like that instead of > having to rebuild all the major parts? > > Thanks! > Best regards > > On 06/11/2018 01:51 PM, Raslan Darawsheh wrote: >> I think you can upgrade the current version that you have as seen in this >> article: >> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs >> .openvswitch.org%2Fen%2Flatest%2Fintro%2Finstall%2Fgeneral%2F%23hot-up >> grading=02%7C01%7Crasland%40mellanox.com%7Cfdaa105976c744dba2f908 >> d5cf9394cc%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C1%7C63664315514160 >> 5703=VhpqI3M4RdnD5Shpbt6O8YmufIKiyoYK9kxO9TR1Yrk%3D=0 >> >> but, I haven't tried it before. >> >> Kindest regards, >> Raslan Darawsheh >> >> -Original Message----- >> From: Tobias Urdin [mailto:tobias.ur...@crystone.com] >> Sent: Monday, June 11, 2018 2:45 PM >> To: Raslan Darawsheh >> Cc: users@dpdk.org >> Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch >> >> Is there any to skip compiling DPDK and OVS+OVS-DPDK and instead use the >> ones I have installed? >> Only compiling the Mellanox PMD module/binary or something similar to that? >> >> I can see that other drivers supply pmd packages like below. >> >> $dpkg -l | grep -E "openvswitch|pmd|dpdk" >> ii dpdk >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (runtime) >> ii librte-pmd-af-packet17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-af-packet runtime library) >> ii librte-pmd-ark17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte_pmd_ark runtime library) >> ii librte-pmd-avp17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte_pmd_avp runtime library) >> ii librte-pmd-bnxt17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-bnxt runtime library) >> ii librte-pmd-bond17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-bond runtime library) ii >> librte-pmd-crypto-scheduler17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte_pmd_crypto_scheduler runtime library) >> ii librte-pmd-cxgbe17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-cxgbe runtime library) >> ii librte-pmd-e1000-17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-e1000 runtime library) >> ii librte-pmd-ena17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-ena runtime library) >> ii librte-pmd-enic17.11:amd64 >> 17.11.1-6~cloud0amd64Data Plane >> Development Kit (librte-pmd-enic runtime library) >> ii librte-pmd-failsaf
Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
I think OVS-DPDK has static linking for dpdk and I'm not sure you can do it this way Kindest regards, Raslan Darawsheh -Original Message- From: Tobias Urdin [mailto:tobias.ur...@crystone.com] Sent: Monday, June 11, 2018 3:05 PM To: Raslan Darawsheh Cc: users@dpdk.org Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch Ok, I'm more wondering if there is any way I can build a librte-pmd-mlx4 package that supplies the compiled PMD or something like that instead of having to rebuild all the major parts? Thanks! Best regards On 06/11/2018 01:51 PM, Raslan Darawsheh wrote: > I think you can upgrade the current version that you have as seen in this > article: > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs > .openvswitch.org%2Fen%2Flatest%2Fintro%2Finstall%2Fgeneral%2F%23hot-up > grading=02%7C01%7Crasland%40mellanox.com%7Cfdaa105976c744dba2f908 > d5cf9394cc%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C1%7C63664315514160 > 5703=VhpqI3M4RdnD5Shpbt6O8YmufIKiyoYK9kxO9TR1Yrk%3D=0 > > but, I haven't tried it before. > > Kindest regards, > Raslan Darawsheh > > -Original Message- > From: Tobias Urdin [mailto:tobias.ur...@crystone.com] > Sent: Monday, June 11, 2018 2:45 PM > To: Raslan Darawsheh > Cc: users@dpdk.org > Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch > > Is there any to skip compiling DPDK and OVS+OVS-DPDK and instead use the ones > I have installed? > Only compiling the Mellanox PMD module/binary or something similar to that? > > I can see that other drivers supply pmd packages like below. > > $dpkg -l | grep -E "openvswitch|pmd|dpdk" > ii dpdk > 17.11.1-6~cloud0amd64Data Plane > Development Kit (runtime) > ii librte-pmd-af-packet17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-af-packet runtime library) > ii librte-pmd-ark17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte_pmd_ark runtime library) > ii librte-pmd-avp17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte_pmd_avp runtime library) > ii librte-pmd-bnxt17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-bnxt runtime library) > ii librte-pmd-bond17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-bond runtime library) ii > librte-pmd-crypto-scheduler17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte_pmd_crypto_scheduler runtime library) > ii librte-pmd-cxgbe17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-cxgbe runtime library) > ii librte-pmd-e1000-17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-e1000 runtime library) > ii librte-pmd-ena17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-ena runtime library) > ii librte-pmd-enic17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-enic runtime library) > ii librte-pmd-failsafe17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-failsafe runtime library) > ii librte-pmd-fm10k17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-fm10k runtime library) > ii librte-pmd-i40e17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-i40e runtime library) > ii librte-pmd-ixgbe17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte-pmd-ixgbe runtime library) > ii librte-pmd-kni17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte_pmd_kni runtime library) > ii librte-pmd-lio17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte_pmd_lio runtime library) > ii librte-pmd-nfp17.11:amd64 > 17.11.1-6~cloud0amd64Data Plane > Development Kit (librte_pmd_nfp runtime library) > ii librte-pmd-null-crypto17.11:amd64 > 17.11.1-6~cloud0amd64
Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
I think you can upgrade the current version that you have as seen in this article: http://docs.openvswitch.org/en/latest/intro/install/general/#hot-upgrading but, I haven't tried it before. Kindest regards, Raslan Darawsheh -Original Message- From: Tobias Urdin [mailto:tobias.ur...@crystone.com] Sent: Monday, June 11, 2018 2:45 PM To: Raslan Darawsheh Cc: users@dpdk.org Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch Is there any to skip compiling DPDK and OVS+OVS-DPDK and instead use the ones I have installed? Only compiling the Mellanox PMD module/binary or something similar to that? I can see that other drivers supply pmd packages like below. $dpkg -l | grep -E "openvswitch|pmd|dpdk" ii dpdk 17.11.1-6~cloud0amd64Data Plane Development Kit (runtime) ii librte-pmd-af-packet17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-af-packet runtime library) ii librte-pmd-ark17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_ark runtime library) ii librte-pmd-avp17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_avp runtime library) ii librte-pmd-bnxt17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-bnxt runtime library) ii librte-pmd-bond17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-bond runtime library) ii librte-pmd-crypto-scheduler17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_crypto_scheduler runtime library) ii librte-pmd-cxgbe17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-cxgbe runtime library) ii librte-pmd-e1000-17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-e1000 runtime library) ii librte-pmd-ena17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-ena runtime library) ii librte-pmd-enic17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-enic runtime library) ii librte-pmd-failsafe17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-failsafe runtime library) ii librte-pmd-fm10k17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-fm10k runtime library) ii librte-pmd-i40e17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-i40e runtime library) ii librte-pmd-ixgbe17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-ixgbe runtime library) ii librte-pmd-kni17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_kni runtime library) ii librte-pmd-lio17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_lio runtime library) ii librte-pmd-nfp17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_nfp runtime library) ii librte-pmd-null-crypto17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-null-crypto runtime library) ii librte-pmd-null17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-null runtime library) ii librte-pmd-octeontx-ssovf17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_octeontx_ssovf runtime library) ii librte-pmd-octeontx17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_octeontx runtime library) ii librte-pmd-pcap17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-pcap runtime library) ii librte-pmd-qede17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-qede runtime library) ii librte-pmd-ring17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-ring runtime library) ii librte-pmd-sfc-efx17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_sfc_efx runtime library) ii librte-pmd-skeleton-event17.11:amd64 17.11.
Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
librte-pmd-tap17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_tap runtime library) ii librte-pmd-thunderx-nicvf17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte_pmd_thunderx_nicvf runtime library) ii librte-pmd-vhost17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-vhost runtime library) ii librte-pmd-virtio17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-virtio runtime library) ii librte-pmd-vmxnet3-uio17.11:amd64 17.11.1-6~cloud0amd64Data Plane Development Kit (librte-pmd-vmxnet3-uio runtime library) ii openvswitch-common 2.9.0-0ubuntu1~cloud0 amd64Open vSwitch common components ii openvswitch-switch 2.9.0-0ubuntu1~cloud0 amd64Open vSwitch switch implementations ii openvswitch-switch-dpdk 2.9.0-0ubuntu1~cloud0 amd64DPDK enabled Open vSwitch switch implementation ii python-openvswitch 2.9.0-0ubuntu1~cloud0 all Python bindings for Open vSwitch Thanks for all the help! Best regards On 06/11/2018 01:37 PM, Raslan Darawsheh wrote: > You can refer to this community page for compiling OVS-DPDK with MLX pmds > enabled: > https://community.mellanox.com/docs/DOC-2637 > > > Kindest regards, > Raslan Darawsheh > > -Original Message- > From: Tobias Urdin [mailto:tobias.ur...@crystone.com] > Sent: Monday, June 11, 2018 2:35 PM > To: Raslan Darawsheh > Cc: users@dpdk.org > Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch > > I haven't compiled any DPDK or Mellanox related modules/packages. > What I have is ovs, ovs-dpdk, mlx4 module, I have also loaded the ib_uverbs > driver. > > Is it the librte_pmd_mlx4 I have to compile manually? > > Do you know any updated documentation about this, there isn't much relevant > and searching for documentation and the correct mlnx driver and code is a > struggle. > > Best regards > > On 06/11/2018 01:20 PM, Raslan Darawsheh wrote: >> From what I'm seeing it looks like it didn't prop the MLX4 device at all. >> Can you make sure you have it enabled in your DPDK package when you compiled >> DPDK ? >> >> Kindest regards, >> Raslan Darawsheh >> >> -Original Message- >> From: Tobias Urdin [mailto:tobias.ur...@crystone.com] >> Sent: Monday, June 11, 2018 2:16 PM >> To: Raslan Darawsheh >> Cc: users@dpdk.org >> Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch >> >> Ok, here is the complete log when restarting the openvswitch-switch service, >> see below. >> >> Also here is the kernel for information: >> $uname -r >> 4.4.0-127-generic >> >> 2018-06-11T11:13:42.729Z|00176|bridge|INFO|bridge br-mlx: deleted >> interface br-mlx on port 65534 >> 2018-06-11T11:13:43.274Z|00177|bridge|INFO|bridge br-int: deleted >> interface br-int on port 65534 >> 2018-06-11T11:13:43.275Z|00178|bridge|INFO|bridge br-int: deleted >> interface int-br-ex on port 1 >> 2018-06-11T11:13:43.275Z|00179|bridge|INFO|bridge br-int: deleted >> interface patch-tun on port 2 >> 2018-06-11T11:13:43.762Z|00180|bridge|INFO|bridge br-tun: deleted >> interface patch-int on port 1 >> 2018-06-11T11:13:43.762Z|00181|bridge|INFO|bridge br-tun: deleted >> interface br-tun on port 65534 >> 2018-06-11T11:13:44.231Z|00182|bridge|INFO|bridge br-ex: deleted >> interface br-ex on port 65534 >> 2018-06-11T11:13:44.232Z|00183|bridge|INFO|bridge br-ex: deleted >> interface phy-br-ex on port 1 >> 2018-06-11T11:13:45.245Z|1|vlog|INFO|opened log file >> /var/log/openvswitch/ovs-vswitchd.log >> 2018-06-11T11:13:45.252Z|2|ovs_numa|INFO|Discovered 40 CPU cores >> on NUMA node 0 2018-06-11T11:13:45.252Z|3|ovs_numa|INFO|Discovered >> 40 CPU cores on NUMA node 1 >> 2018-06-11T11:13:45.252Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes >> and >> 80 CPU cores >> 2018-06-11T11:13:45.252Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >> connecting... >> 2018-06-11T11:13:45.252Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >> connected >> 2018-06-11T11:13:45.256Z|7|dpdk|INFO|Using DPDK 17.11.0 >> 2018-06-11T11:13:45.256Z|8|dpdk|INFO|DPDK Enabled - initializing... >> 2018-06-11T11:13:45.256Z|9|dpdk|INFO|No vhost-sock-dir provided - >> defaulting to /var/
Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
You can refer to this community page for compiling OVS-DPDK with MLX pmds enabled: https://community.mellanox.com/docs/DOC-2637 Kindest regards, Raslan Darawsheh -Original Message- From: Tobias Urdin [mailto:tobias.ur...@crystone.com] Sent: Monday, June 11, 2018 2:35 PM To: Raslan Darawsheh Cc: users@dpdk.org Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch I haven't compiled any DPDK or Mellanox related modules/packages. What I have is ovs, ovs-dpdk, mlx4 module, I have also loaded the ib_uverbs driver. Is it the librte_pmd_mlx4 I have to compile manually? Do you know any updated documentation about this, there isn't much relevant and searching for documentation and the correct mlnx driver and code is a struggle. Best regards On 06/11/2018 01:20 PM, Raslan Darawsheh wrote: > From what I'm seeing it looks like it didn't prop the MLX4 device at all. > Can you make sure you have it enabled in your DPDK package when you compiled > DPDK ? > > Kindest regards, > Raslan Darawsheh > > -Original Message- > From: Tobias Urdin [mailto:tobias.ur...@crystone.com] > Sent: Monday, June 11, 2018 2:16 PM > To: Raslan Darawsheh > Cc: users@dpdk.org > Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch > > Ok, here is the complete log when restarting the openvswitch-switch service, > see below. > > Also here is the kernel for information: > $uname -r > 4.4.0-127-generic > > 2018-06-11T11:13:42.729Z|00176|bridge|INFO|bridge br-mlx: deleted > interface br-mlx on port 65534 > 2018-06-11T11:13:43.274Z|00177|bridge|INFO|bridge br-int: deleted > interface br-int on port 65534 > 2018-06-11T11:13:43.275Z|00178|bridge|INFO|bridge br-int: deleted > interface int-br-ex on port 1 > 2018-06-11T11:13:43.275Z|00179|bridge|INFO|bridge br-int: deleted > interface patch-tun on port 2 > 2018-06-11T11:13:43.762Z|00180|bridge|INFO|bridge br-tun: deleted > interface patch-int on port 1 > 2018-06-11T11:13:43.762Z|00181|bridge|INFO|bridge br-tun: deleted > interface br-tun on port 65534 > 2018-06-11T11:13:44.231Z|00182|bridge|INFO|bridge br-ex: deleted > interface br-ex on port 65534 > 2018-06-11T11:13:44.232Z|00183|bridge|INFO|bridge br-ex: deleted > interface phy-br-ex on port 1 > 2018-06-11T11:13:45.245Z|1|vlog|INFO|opened log file > /var/log/openvswitch/ovs-vswitchd.log > 2018-06-11T11:13:45.252Z|2|ovs_numa|INFO|Discovered 40 CPU cores > on NUMA node 0 2018-06-11T11:13:45.252Z|3|ovs_numa|INFO|Discovered > 40 CPU cores on NUMA node 1 > 2018-06-11T11:13:45.252Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes > and > 80 CPU cores > 2018-06-11T11:13:45.252Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock: > connecting... > 2018-06-11T11:13:45.252Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock: > connected > 2018-06-11T11:13:45.256Z|7|dpdk|INFO|Using DPDK 17.11.0 > 2018-06-11T11:13:45.256Z|8|dpdk|INFO|DPDK Enabled - initializing... > 2018-06-11T11:13:45.256Z|9|dpdk|INFO|No vhost-sock-dir provided - > defaulting to /var/run/openvswitch > 2018-06-11T11:13:45.256Z|00010|dpdk|INFO|IOMMU support for vhost-user-client > disabled. > 2018-06-11T11:13:45.256Z|00011|dpdk|INFO|EAL ARGS: ovs-vswitchd > --socket-mem 1024,0 -c 0x0001 > 2018-06-11T11:13:45.258Z|00012|dpdk|INFO|EAL: Detected 80 lcore(s) > 2018-06-11T11:13:45.285Z|00013|dpdk|INFO|EAL: Probing VFIO support... > 2018-06-11T11:13:45.285Z|00014|dpdk|INFO|EAL: VFIO support initialized > 2018-06-11T11:13:48.214Z|00015|dpdk|INFO|EAL: PCI device :01:00.0 on NUMA > socket 0 > 2018-06-11T11:13:48.214Z|00016|dpdk|INFO|EAL: probe driver: 8086:1521 > net_e1000_igb > 2018-06-11T11:13:48.214Z|00017|dpdk|INFO|EAL: PCI device :01:00.1 on NUMA > socket 0 > 2018-06-11T11:13:48.214Z|00018|dpdk|INFO|EAL: probe driver: 8086:1521 > net_e1000_igb > 2018-06-11T11:13:48.214Z|00019|dpdk|INFO|EAL: PCI device :18:00.0 on NUMA > socket 0 > 2018-06-11T11:13:48.214Z|00020|dpdk|INFO|EAL: probe driver: 8086:1572 > net_i40e > 2018-06-11T11:13:48.214Z|00021|dpdk|INFO|EAL: PCI device :18:00.1 on NUMA > socket 0 > 2018-06-11T11:13:48.214Z|00022|dpdk|INFO|EAL: probe driver: 8086:1572 > net_i40e > 2018-06-11T11:13:48.214Z|00023|dpdk|INFO|DPDK pdump packet capture > enabled 2018-06-11T11:13:48.224Z|00024|dpdk|INFO|DPDK Enabled - > initialized > 2018-06-11T11:13:48.235Z|00025|ofproto_dpif|INFO|netdev@ovs-netdev: > Datapath supports recirculation > 2018-06-11T11:13:48.235Z|00026|ofproto_dpif|INFO|netdev@ovs-netdev: > VLAN header stack length probed as 1 > 2018-06-11T11:13:48.235Z|00027|ofproto_dpif|INFO|netdev@ovs-netdev: > MPLS label stack length probed as 3 > 2018-06-11T11:13:48.235Z|00028|ofproto_dpif|INFO|netdev@ovs-netdev: >
Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
I haven't compiled any DPDK or Mellanox related modules/packages. What I have is ovs, ovs-dpdk, mlx4 module, I have also loaded the ib_uverbs driver. Is it the librte_pmd_mlx4 I have to compile manually? Do you know any updated documentation about this, there isn't much relevant and searching for documentation and the correct mlnx driver and code is a struggle. Best regards On 06/11/2018 01:20 PM, Raslan Darawsheh wrote: > From what I'm seeing it looks like it didn't prop the MLX4 device at all. > Can you make sure you have it enabled in your DPDK package when you compiled > DPDK ? > > Kindest regards, > Raslan Darawsheh > > -Original Message- > From: Tobias Urdin [mailto:tobias.ur...@crystone.com] > Sent: Monday, June 11, 2018 2:16 PM > To: Raslan Darawsheh > Cc: users@dpdk.org > Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch > > Ok, here is the complete log when restarting the openvswitch-switch service, > see below. > > Also here is the kernel for information: > $uname -r > 4.4.0-127-generic > > 2018-06-11T11:13:42.729Z|00176|bridge|INFO|bridge br-mlx: deleted interface > br-mlx on port 65534 2018-06-11T11:13:43.274Z|00177|bridge|INFO|bridge > br-int: deleted interface br-int on port 65534 > 2018-06-11T11:13:43.275Z|00178|bridge|INFO|bridge br-int: deleted interface > int-br-ex on port 1 2018-06-11T11:13:43.275Z|00179|bridge|INFO|bridge br-int: > deleted interface patch-tun on port 2 > 2018-06-11T11:13:43.762Z|00180|bridge|INFO|bridge br-tun: deleted interface > patch-int on port 1 2018-06-11T11:13:43.762Z|00181|bridge|INFO|bridge br-tun: > deleted interface br-tun on port 65534 > 2018-06-11T11:13:44.231Z|00182|bridge|INFO|bridge br-ex: deleted interface > br-ex on port 65534 2018-06-11T11:13:44.232Z|00183|bridge|INFO|bridge br-ex: > deleted interface phy-br-ex on port 1 > 2018-06-11T11:13:45.245Z|1|vlog|INFO|opened log file > /var/log/openvswitch/ovs-vswitchd.log > 2018-06-11T11:13:45.252Z|2|ovs_numa|INFO|Discovered 40 CPU cores on NUMA > node 0 2018-06-11T11:13:45.252Z|3|ovs_numa|INFO|Discovered 40 CPU cores > on NUMA node 1 2018-06-11T11:13:45.252Z|4|ovs_numa|INFO|Discovered 2 NUMA > nodes and > 80 CPU cores > 2018-06-11T11:13:45.252Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock: > connecting... > 2018-06-11T11:13:45.252Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock: > connected > 2018-06-11T11:13:45.256Z|7|dpdk|INFO|Using DPDK 17.11.0 > 2018-06-11T11:13:45.256Z|8|dpdk|INFO|DPDK Enabled - initializing... > 2018-06-11T11:13:45.256Z|9|dpdk|INFO|No vhost-sock-dir provided - > defaulting to /var/run/openvswitch > 2018-06-11T11:13:45.256Z|00010|dpdk|INFO|IOMMU support for vhost-user-client > disabled. > 2018-06-11T11:13:45.256Z|00011|dpdk|INFO|EAL ARGS: ovs-vswitchd --socket-mem > 1024,0 -c 0x0001 > 2018-06-11T11:13:45.258Z|00012|dpdk|INFO|EAL: Detected 80 lcore(s) > 2018-06-11T11:13:45.285Z|00013|dpdk|INFO|EAL: Probing VFIO support... > 2018-06-11T11:13:45.285Z|00014|dpdk|INFO|EAL: VFIO support initialized > 2018-06-11T11:13:48.214Z|00015|dpdk|INFO|EAL: PCI device :01:00.0 on NUMA > socket 0 > 2018-06-11T11:13:48.214Z|00016|dpdk|INFO|EAL: probe driver: 8086:1521 > net_e1000_igb > 2018-06-11T11:13:48.214Z|00017|dpdk|INFO|EAL: PCI device :01:00.1 on NUMA > socket 0 > 2018-06-11T11:13:48.214Z|00018|dpdk|INFO|EAL: probe driver: 8086:1521 > net_e1000_igb > 2018-06-11T11:13:48.214Z|00019|dpdk|INFO|EAL: PCI device :18:00.0 on NUMA > socket 0 > 2018-06-11T11:13:48.214Z|00020|dpdk|INFO|EAL: probe driver: 8086:1572 > net_i40e > 2018-06-11T11:13:48.214Z|00021|dpdk|INFO|EAL: PCI device :18:00.1 on NUMA > socket 0 > 2018-06-11T11:13:48.214Z|00022|dpdk|INFO|EAL: probe driver: 8086:1572 > net_i40e > 2018-06-11T11:13:48.214Z|00023|dpdk|INFO|DPDK pdump packet capture enabled > 2018-06-11T11:13:48.224Z|00024|dpdk|INFO|DPDK Enabled - initialized > 2018-06-11T11:13:48.235Z|00025|ofproto_dpif|INFO|netdev@ovs-netdev: > Datapath supports recirculation > 2018-06-11T11:13:48.235Z|00026|ofproto_dpif|INFO|netdev@ovs-netdev: VLAN > header stack length probed as 1 > 2018-06-11T11:13:48.235Z|00027|ofproto_dpif|INFO|netdev@ovs-netdev: MPLS > label stack length probed as 3 > 2018-06-11T11:13:48.235Z|00028|ofproto_dpif|INFO|netdev@ovs-netdev: > Datapath supports truncate action > 2018-06-11T11:13:48.235Z|00029|ofproto_dpif|INFO|netdev@ovs-netdev: > Datapath supports unique flow ids > 2018-06-11T11:13:48.235Z|00030|ofproto_dpif|INFO|netdev@ovs-netdev: > Datapath supports clone action > 2018-06-11T11:13:48.235Z|00031|ofproto_dpif|INFO|netdev@ovs-netdev: Max > sample nesting level probed as 10 > 2018-06-11T11:13:48.235Z|00032|ofproto_dpif|INFO|
Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
>From what I'm seeing it looks like it didn't prop the MLX4 device at all. Can you make sure you have it enabled in your DPDK package when you compiled DPDK ? Kindest regards, Raslan Darawsheh -Original Message- From: Tobias Urdin [mailto:tobias.ur...@crystone.com] Sent: Monday, June 11, 2018 2:16 PM To: Raslan Darawsheh Cc: users@dpdk.org Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch Ok, here is the complete log when restarting the openvswitch-switch service, see below. Also here is the kernel for information: $uname -r 4.4.0-127-generic 2018-06-11T11:13:42.729Z|00176|bridge|INFO|bridge br-mlx: deleted interface br-mlx on port 65534 2018-06-11T11:13:43.274Z|00177|bridge|INFO|bridge br-int: deleted interface br-int on port 65534 2018-06-11T11:13:43.275Z|00178|bridge|INFO|bridge br-int: deleted interface int-br-ex on port 1 2018-06-11T11:13:43.275Z|00179|bridge|INFO|bridge br-int: deleted interface patch-tun on port 2 2018-06-11T11:13:43.762Z|00180|bridge|INFO|bridge br-tun: deleted interface patch-int on port 1 2018-06-11T11:13:43.762Z|00181|bridge|INFO|bridge br-tun: deleted interface br-tun on port 65534 2018-06-11T11:13:44.231Z|00182|bridge|INFO|bridge br-ex: deleted interface br-ex on port 65534 2018-06-11T11:13:44.232Z|00183|bridge|INFO|bridge br-ex: deleted interface phy-br-ex on port 1 2018-06-11T11:13:45.245Z|1|vlog|INFO|opened log file /var/log/openvswitch/ovs-vswitchd.log 2018-06-11T11:13:45.252Z|2|ovs_numa|INFO|Discovered 40 CPU cores on NUMA node 0 2018-06-11T11:13:45.252Z|3|ovs_numa|INFO|Discovered 40 CPU cores on NUMA node 1 2018-06-11T11:13:45.252Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes and 80 CPU cores 2018-06-11T11:13:45.252Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting... 2018-06-11T11:13:45.252Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected 2018-06-11T11:13:45.256Z|7|dpdk|INFO|Using DPDK 17.11.0 2018-06-11T11:13:45.256Z|8|dpdk|INFO|DPDK Enabled - initializing... 2018-06-11T11:13:45.256Z|9|dpdk|INFO|No vhost-sock-dir provided - defaulting to /var/run/openvswitch 2018-06-11T11:13:45.256Z|00010|dpdk|INFO|IOMMU support for vhost-user-client disabled. 2018-06-11T11:13:45.256Z|00011|dpdk|INFO|EAL ARGS: ovs-vswitchd --socket-mem 1024,0 -c 0x0001 2018-06-11T11:13:45.258Z|00012|dpdk|INFO|EAL: Detected 80 lcore(s) 2018-06-11T11:13:45.285Z|00013|dpdk|INFO|EAL: Probing VFIO support... 2018-06-11T11:13:45.285Z|00014|dpdk|INFO|EAL: VFIO support initialized 2018-06-11T11:13:48.214Z|00015|dpdk|INFO|EAL: PCI device :01:00.0 on NUMA socket 0 2018-06-11T11:13:48.214Z|00016|dpdk|INFO|EAL: probe driver: 8086:1521 net_e1000_igb 2018-06-11T11:13:48.214Z|00017|dpdk|INFO|EAL: PCI device :01:00.1 on NUMA socket 0 2018-06-11T11:13:48.214Z|00018|dpdk|INFO|EAL: probe driver: 8086:1521 net_e1000_igb 2018-06-11T11:13:48.214Z|00019|dpdk|INFO|EAL: PCI device :18:00.0 on NUMA socket 0 2018-06-11T11:13:48.214Z|00020|dpdk|INFO|EAL: probe driver: 8086:1572 net_i40e 2018-06-11T11:13:48.214Z|00021|dpdk|INFO|EAL: PCI device :18:00.1 on NUMA socket 0 2018-06-11T11:13:48.214Z|00022|dpdk|INFO|EAL: probe driver: 8086:1572 net_i40e 2018-06-11T11:13:48.214Z|00023|dpdk|INFO|DPDK pdump packet capture enabled 2018-06-11T11:13:48.224Z|00024|dpdk|INFO|DPDK Enabled - initialized 2018-06-11T11:13:48.235Z|00025|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports recirculation 2018-06-11T11:13:48.235Z|00026|ofproto_dpif|INFO|netdev@ovs-netdev: VLAN header stack length probed as 1 2018-06-11T11:13:48.235Z|00027|ofproto_dpif|INFO|netdev@ovs-netdev: MPLS label stack length probed as 3 2018-06-11T11:13:48.235Z|00028|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports truncate action 2018-06-11T11:13:48.235Z|00029|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports unique flow ids 2018-06-11T11:13:48.235Z|00030|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports clone action 2018-06-11T11:13:48.235Z|00031|ofproto_dpif|INFO|netdev@ovs-netdev: Max sample nesting level probed as 10 2018-06-11T11:13:48.235Z|00032|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports eventmask in conntrack action 2018-06-11T11:13:48.235Z|00033|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_clear action 2018-06-11T11:13:48.235Z|00034|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_state 2018-06-11T11:13:48.235Z|00035|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_zone 2018-06-11T11:13:48.235Z|00036|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_mark 2018-06-11T11:13:48.235Z|00037|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_label 2018-06-11T11:13:48.235Z|00038|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_state_nat 2018-06-11T11:13:48.235Z|00039|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_orig_tuple 2018-06-11T11:13:48.235Z|00040|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_orig_tuple6 2018-06-11T11
Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
31Z|00134|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.9.0 2018-06-11T11:13:53.662Z|00135|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.662Z|00136|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.662Z|00137|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.675Z|00138|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.675Z|00139|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.675Z|00140|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.682Z|00141|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.682Z|00142|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.682Z|00143|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.693Z|00144|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.693Z|00145|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.693Z|00146|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.705Z|00147|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.705Z|00148|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.705Z|00149|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.711Z|00150|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.711Z|00151|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.711Z|00152|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.717Z|00153|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.717Z|00154|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.717Z|00155|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.728Z|00156|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.728Z|00157|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.728Z|00158|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.743Z|00159|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.743Z|00160|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.743Z|00161|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.749Z|00162|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.749Z|00163|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.749Z|00164|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.756Z|00165|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.756Z|00166|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.756Z|00167|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:53.766Z|00168|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0' 2018-06-11T11:13:53.766Z|00169|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK 2018-06-11T11:13:53.766Z|00170|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument) 2018-06-11T11:13:55.270Z|00171|memory|INFO|1406100 kB peak resident set size after 10.0 seconds 2018-06-11T11:13:55.270Z|00172|memory|INFO|handlers:118 ofconns:3 ports:8 revalidators:42 rules:36 udpif keys:1 2018-06-11T11:14:03.699Z|00173|connmgr|INFO|br-int<->tcp:127.0.0.1:6633: 5 flow_mods 10 s ago (5 adds) 2018-06-11T11:14:03.737Z|00174|connmgr|INFO|br-ex<->tcp:127.0.0.1:6633: 2 flow_mods 10 s ago (2 adds) 2018-06-11T11:14:03.773Z|00175|connmgr|INFO|br-tun<->tcp:127.0.0.1:6633: 12 flow_mods 10 s ago (12 adds) Best regards On 06/11/2018 12:57 PM, Raslan Darawsheh wrote: > What I really want to see is the init process for OVS-DPDK that dumps the > DPDK initialization. > I think you will find it at the beginning of the log that you just sent. > > Kindest regards, > Raslan Darawsheh > > -----Original Message----- > From: Tobias Urdin [mailto:tobias.ur...@crystone.com] > Sent: Monday, June 11, 2018 1:00 PM > To: Raslan Darawsheh > Cc: users@dpdk.org > Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch > > Hello Raslan, > Thank you for your reply. > > For reference the br-mlx bridge was created like this: > $ovs-vsctl add-br br-mlx -- set bridge br-mlx datapath_type=netdev > > $ovs-vsctl add-port br-mlx enp59s0d1 -- set Interface enp59s0d1 type=dpdk > options:dpdk-devargs=mlx4_0 > ovs-vsctl: Error detected while setting up 'enp59s0d1': Error attaching > device 'mlx4_0' to DPDK. See ovs-vswitchd log for details. > ovs-vsctl: The default log directory is "/var
