Perhaps someone from MLNX can confirm, but this is what we received from them...but we haven’t had a chance to verify yet.
======================== Since DPDK 17.11 Mellanox PMD moved to work on top of upstream user space libraries (rdma-core) instead of the Mellanox proprietary ones. So the prerequisites to compile Mellanox PMDs has changed. Please read carefully the user manual  The errors are because rdma-core is not installed on the setup. There are 2 options: 1. Install Mellanox OFED with ./mlnxofedinstall --upstream-libs –dpdk which will install the rdma-core part as well. 2. Take rdma-core from upstream and upgrade the kernel to the minimum version required. Let me know if you still have issues.  http://dpdk.org/doc/guides/nics/mlx5.html ======================== Wanted to ask you a quick question about plans to support Mellanox compilation with DPDK 17.11 with vpp. Current release of vpp – vpp 18.01 - moved to this DPDK. Previous DPDK 17.08 compiles fine with Mellanox support, however DPDK 17.11 fails (log attached for reference). Could you please tell us what is your support level for DPDK 17.11? I remember Shachar mentioned some rework in progress for this, but I don’t recall the details. ========================= On 2/14/18, 9:02 AM, "email@example.com on behalf of John Lo (loj)" <firstname.lastname@example.org on behalf of l...@cisco.com> wrote: Hi Avi, I do not have direct experience myself but someone told me Mellanox DPDK driver is broken with DPDK 17.11. You may need to rebuild VPP 18.01 with DPDK 17.08 to get Melllanox NICs to work. Hopefully someone with direct Mellanox experience can add more details. Regards, John -----Original Message----- From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Avi Cohen (A) Sent: Wednesday, February 14, 2018 10:19 AM To: email@example.com Subject: Re: [vpp-dev] Mellanox Connectx-4 - /nasm-2.13.01: No such file or directory To run dpdk on connect-4 - I'm following the steps as per https://community.mellanox.com/docs/DOC-2729 to run dpdk on connect-4 But failed in make dpdk-install-dev DPDK_MLX5_PMD=y Getting these error /bin/bash: line 0: cd: /home/avi/vpp/dpdk/deb/_build/nasm-2.13.01: No such file or directory Makefile:317: recipe for target 'build-nasm' failed make: *** [build-nasm] Error 1 make: Leaving directory '/home/avi/vpp/dpdk' debian/rules:27: recipe for target 'override_dh_install' failed make: *** [override_dh_install] Error 2 make: Leaving directory '/home/avi/vpp/dpdk/deb' debian/rules:18: recipe for target 'binary' failed make: *** [binary] Error 2 make: Leaving directory '/home/avi/vpp/dpdk/deb' dpkg-buildpackage: error: debian/rules binary gave error exit status 2 Makefile:382: recipe for target 'vpp-dpdk-dev_17.08-vpp2_amd64.deb' failed make: *** [vpp-dpdk-dev_17.08-vpp2_amd64.deb] Error 2 make: Leaving directory '/home/avi/vpp/dpdk' Makefile:389: recipe for target 'install-deb' failed make: *** [install-deb] Error 2 make: Leaving directory '/home/avi/vpp/dpdk' Makefile:464: recipe for target 'dpdk-install-dev' failed make: *** [dpdk-install-dev] Error 2 > -----Original Message----- > From: Avi Cohen (A) > Sent: Wednesday, 14 February, 2018 4:49 PM > To: firstname.lastname@example.org > Subject: Mellanox Connectx-4 > > Hello > I added 2 Mellanox Connectx-4 PCI devices to the whitelist > startup.conf and restarted VPP. > But don't see them in vppctl show interfaces I can run other > dpdk-apps w these interfaces without a problem. > > Who can assist ? > Best Regards > Avi -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8227): https://lists.fd.io/g/vpp-dev/message/8227 View All Messages In Topic (3): https://lists.fd.io/g/vpp-dev/topic/11350571 Mute This Topic: https://lists.fd.io/mt/11350571/21656 New Topic: https://lists.fd.io/g/vpp-dev/post Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656 Group Home: https://lists.fd.io/g/vpp-dev Contact Group Owner: vpp-dev+ow...@lists.fd.io Terms of Service: https://lists.fd.io/static/tos Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub -=-=-=-=-=-=-=-=-=-=-=-