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 [1]
The errors are because rdma-core is not installed on the setup. There are 2 
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.

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, " on behalf of John Lo (loj)" 
< on behalf of> 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.   
    -----Original Message-----
    From: [] On Behalf Of Avi 
Cohen (A)
    Sent: Wednesday, February 14, 2018 10:19 AM
    Subject: Re: [vpp-dev] Mellanox Connectx-4 - /nasm-2.13.01: No such file or 
    To run dpdk on connect-4 - I'm following the steps  as per  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[5]: *** [build-nasm] Error 1
    make[5]: Leaving directory '/home/avi/vpp/dpdk'
    debian/rules:27: recipe for target 'override_dh_install' failed
    make[4]: *** [override_dh_install] Error 2
    make[4]: Leaving directory '/home/avi/vpp/dpdk/deb'
    debian/rules:18: recipe for target 'binary' failed
    make[3]: *** [binary] Error 2
    make[3]: 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[2]: *** [vpp-dpdk-dev_17.08-vpp2_amd64.deb] Error 2
    make[2]: Leaving directory '/home/avi/vpp/dpdk'
    Makefile:389: recipe for target 'install-deb' failed
    make[1]: *** [install-deb] Error 2
    make[1]: 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:
    > 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


You receive all messages sent to this group.

View/Reply Online (#8227):
View All Messages In Topic (3):
Mute This Topic:
New Topic:

Change Your Subscription:
Group Home:
Contact Group Owner:
Terms of Service:

Reply via email to