No, specific reason. When I enabled MLX5 NICs and compilation (as mentioned in trail mail) of VPP (stable/2009 branch) code was successful. But I got the below error while running VPP: /usr/bin/vpp: symbol lookup error: /usr/lib/librte_pmd_mlx5_glue.so.20.02.0: undefined symbol: mlx5_malloc
After applying the below patch, above issue resolved and able to see the interfaces. https://inbox.dpdk.org/stable/20201027101503.16295-1-ophi...@nvidia.com/T/ Thanks for your help, Varun -----Original Message----- From: Benoit Ganne (bganne) <bga...@cisco.com> Sent: Tuesday, December 21, 2021 4:04 PM To: 汪翰林 <hanlin_w...@163.com>; Varun Rapelly <vrape...@marvell.com> Cc: format_...@outlook.com; mgsm...@netgate.com; vpp-dev@lists.fd.io Subject: [EXT] RE: [vpp-dev] MLX5 NIC interface is not visible External Email ---------------------------------------------------------------------- Any reason for not using the rdma driver? This is usually the one we use for Mellanox, and it should work out-of-the-box. Best ben > -----Original Message----- > From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of ??? > Sent: mardi 21 décembre 2021 10:47 > To: vrape...@marvell.com > Cc: format_...@outlook.com; mgsm...@netgate.com; vpp-dev@lists.fd.io > Subject: Re: [vpp-dev] MLX5 NIC interface is not visible > > You can try to add "vpp_uses_dpdk_mlx5_pmd = yes" to build- > data/platforms/vpp.mk. > > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__maas.mail.163.co > m_dashi-2Dweb-2D&d=DwIGaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=Ls9yYo1p46pLD7Ycp > e9zQMH7Aeg3urIoxD8M2j9njaI&m=r6asQGPvdDJakngGsc1r6MSFnNDm7_YDgx9Klvm6a > JaSkb3bR0CxDTLCc9AMSGY8&s=y-62VKO9qqc8najmFkCpGgrjP3wSOSvwSmYYywk3yNs& > e= > extend/html/proSignature.html?ftlId=1&name=%E6%B1%AA%E7%BF%B0%E6%9E%97 > &uid > =hanlin_wang%40163.com&iconUrl=https%3A%2F%2Fmail- > online.nosdn.127.net%2Fqiyelogo%2FdefaultAvatar.png&items=%5B%22hanlin > _wan > g%40163.com%22%5D> > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__mail-2Donline.nosdn.127.net_qiyelogo_defaultAvatar.png&d=DwIGaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=Ls9yYo1p46pLD7Ycpe9zQMH7Aeg3urIoxD8M2j9njaI&m=r6asQGPvdDJakngGsc1r6MSFnNDm7_YDgx9Klvm6aJaSkb3bR0CxDTLCc9AMSGY8&s=sSckByOO0h6ZR9GgkUfTeXkJWTzp07ZW6d2CE1Ca9OQ&e= > > 汪翰林 > hanlin_w...@163.com > On 12/19/2021 03:04，Varun Rapelly<vrape...@marvell.com> > <mailto:vrape...@marvell.com> wrote： > > Thanks Matt and Hub for your prompt response. > > > > Option 2 (suggested by Matt) worked fine in master branch. > > > > vpp# sh version > > vpp v22.02-rc0~405-g20c242316 built by root on dellt640_transport-2 > at 2021-12-18T09:24:06 > > > > But if I follow similar steps in VPP stable/2009 branch to include > MLX5 and MLX4 NICs, it’s not working. > > > > root@dellt640-transport-2:~/Varun/vpp_2009_mlx_6# git diff > build/external/packages/dpdk.mk > > diff --git a/build/external/packages/dpdk.mk > b/build/external/packages/dpdk.mk > > index beabf48e9..54cb3ac3c 100644 > > --- a/build/external/packages/dpdk.mk > > +++ b/build/external/packages/dpdk.mk > > @@ -16,8 +16,8 @@ DPDK_CACHE_LINE_SIZE ?= 64 > > DPDK_DOWNLOAD_DIR ?= $(DL_CACHE_DIR) > > DPDK_DEBUG ?= n > > DPDK_AARCH64_GENERIC ?= y > > -DPDK_MLX4_PMD ?= n > > -DPDK_MLX5_PMD ?= n > > +DPDK_MLX4_PMD ?= y > > +DPDK_MLX5_PMD ?= y > > DPDK_TAP_PMD ?= n > > DPDK_FAILSAFE_PMD ?= n > > > > Triggered build using below commands: > > make install-ext-deps > > make pkg-deb PLATFORM=vpp vpp_uses_dpdk_mlx5_pmd=yes > vpp_uses_dpdk_mlx4_pmd=yes > > > > Could you please let me know, that is there any other option that we > need to use in VPP-20.09 branch to enable MLX5/4 NIC (other than above)? > > > > Thanks in advance, > Varun > > From: Юрий Иванов <format_...@outlook.com > <mailto:format_...@outlook.com> > > Sent: Saturday, December 18, 2021 12:36 PM > To: Varun Rapelly <vrape...@marvell.com <mailto:vrape...@marvell.com> > >; mgsm...@netgate.com <mailto:mgsm...@netgate.com> > Cc: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> > Subject: [EXT] RE: [vpp-dev] MLX5 NIC interface is not visible > > > > External Email > > ________________________________ > > If you choose RDMA just look at the example in docs )) > > FD.io VPP: RDMA (ibverb) Ethernet driver > <https://urldefense.proofpoint.com/v2/url?u=https- > 3A__docs.fd.io_vpp_20.01_rdma-5Fdoc.html&d=DwMF- > Q&c=nKjWec2b6R0mOyPaz7xtfQ&r=Ls9yYo1p46pLD7Ycpe9zQMH7Aeg3urIoxD8M2j9nj > aI&m > =QBPgGxKrvsXqiPwFE8Y7WtqSrr2JZXoETpTpKKp9QM9yaIRXmOJm1pQWtvIuz3Kv&s=I2 > o8i- 4UuPDVj9VpeO0ZEhZnAW7ARSArVpKwgO83bJY&e=> > > ________________________________ > > От: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> <vpp- > d...@lists.fd.io <mailto:vpp-dev@lists.fd.io> > от имени Matthew Smith > via lists.fd.io <mgsmith=netgate....@lists.fd.io > <mailto:mgsmith=netgate....@lists.fd.io> > > Отправлено: 17 декабря 2021 г. 22:31 > Кому: Varun Rapelly <vrape...@marvell.com > <mailto:vrape...@marvell.com> > > Копия: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> <vpp- > d...@lists.fd.io <mailto:vpp-dev@lists.fd.io> > > Тема: Re: [vpp-dev] MLX5 NIC interface is not visible > > > > > > Your options are: > > > > 1. Use the rdma plugin and create rdma interfaces. > > 2. Use the DPDK plugin. The DPDK build that is generated when you > build VPP will not include the mellanox PMDs by default. You need to > explicitly enable them when you build. There are build variables named > DPDK_MLX5_PMD and DPDK_MLX5_COMMON_PMD which have default values set > to 'n'. Those need to be set to 'y' to build the mlx5 PMD. You can set > these by running something like 'make DPDK_MLX5_PMD=y > DPDK_MLX5_COMMON_PMD=y pkg-deb', or you could edit > build/external/packages/dpdk.mk > <https://urldefense.proofpoint.com/v2/url?u=http-3A__dpdk.mk&d=DwMF- > Q&c=nKjWec2b6R0mOyPaz7xtfQ&r=Ls9yYo1p46pLD7Ycpe9zQMH7Aeg3urIoxD8M2j9nj > aI&m > =QBPgGxKrvsXqiPwFE8Y7WtqSrr2JZXoETpTpKKp9QM9yaIRXmOJm1pQWtvIuz3Kv&s=Eh > wBc2 0PFZr93BmYiDc_EMvgSVdgMCP4pF_to1GO5O4&e=> and change the > defaults there. > > > > -Matt > > > > > > > > > > On Fri, Dec 17, 2021 at 1:12 PM Varun Rapelly <vrape...@marvell.com > <mailto:vrape...@marvell.com> > wrote: > > Hi, > > > > I’m trying to use ConnectX-5 NIC interfaces in VPP (20.09) > application running on a x86 host (Ubuntu 18.04), but unable to find > this interface in VPP. > > Do we need to create rdma interface to use mlx5 NIC interfaces? > Or > is there any other way to use this? > > > > Below are configuration/NIC and other relevant details: > > vpp# sh interface > > Name Idx State MTU > (L3/IP4/IP6/MPLS) Counter Count > > local0 0 down 0/0/0/0 > > > > VPP startup configuration: > > dpdk { > > dev 0000:d9:00.0 { > > name eth0 > > } > > } > > > > plugins { > > plugin default { enable } > > plugin dpdk_plugin.so {enable } > > } > > > > NIC driver status: > > Network devices using kernel driver > > =================================== > > 0000:d9:00.0 'MT28800 Family [ConnectX-5 Ex] 1019' if=eth4 > drv=mlx5_core unused=uio_pci_generic > > > > vpp# sh pci > > 0000:d9:00.0 1 15b3:1019 8.0 GT/s x16 mlx5_core > CX516A - ConnectX-5 QSFP28 PN: MCX516A-CDAT > > > EC: AA > > > V2: 0x 4d 43 58 35 31 36 41 2d ... > > > SN: MT2017J09203 > > > V3: 0x 39 36 38 37 30 34 64 62 ... > > > VA: 0x 4d 4c 58 3a 4d 4f 44 4c ... > > > V0: 0x 50 43 49 65 47 65 6e 34 ... > > > RV: 0x 08 00 00 > > > > vpp# sh log > > 2021/12/17 18:53:08:339 notice dpdk EAL init > args: -c e -n 4 --in-memory --no-telemetry --file-prefix vpp -a > 0000:d9:00.0 --main-lcore 1 > > 2021/12/17 18:53:08:489 notice dpdk DPDK drivers > found no Ethernet devices... > > > > > > Thanks, > > Varun > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20656): https://lists.fd.io/g/vpp-dev/message/20656 Mute This Topic: https://lists.fd.io/mt/87800334/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
