From: Vineeth Thapeta <vthape2@uic.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Trouble Building DPDK with MLNX OFED(4.4) Works with 5.0
Date: Sat, 6 Jun 2020 15:54:10 -0500 [thread overview]
Message-ID: <CADWAvF7DRcgdC2P=CvyojoKQ5j=6BcLmkGjfZb4V5uBAPtTG4g@mail.gmail.com> (raw)
In-Reply-To: <4178299.QiJXgQhXax@thomas>
Hi Thomas,
We want to use TAS which is built on top of DPDK, I installed Mellanox OFED
5.0 and TAS and everything was good, until we had to install Moogen. Please
find my answer to your questions. Thanks for the prompt reply. I appreciate
it.
We are using Ubuntu 18.04. I indeed had success in installing dpdk 19.11
LTS with MLNX_OFED 5.0. To answer your questions about Moongen either
requires 1) Complete OFED drivers or 2) libibverbs, libmlx5,
mlnx-ofed-kernel packages, These packages are installed with MLNX_ofed
drivers if I am not mistaken. So I moved on to build Moongen, When building
moongen with OFED 5.0 I get the error fatal error: infiniband/mlx5_hw.h: No
such file or directory #include <infiniband/mlx5_hw.h>. I thought this
might be related to the libmlx5 and I installed libmlx5.deb from the
packages in the DEBS/ folder. testpmd stops working with this prompt
./testpmd: /usr/lib/libmlx5.so.1: no version information available
(required by ./testpmd). So I tried rolling back the OFED version to 4.4,
which has caused problems with building dpdk with version 19.11 LTS,18.11
LTS and 17.11 LTS as I shared in the previous mail.
I hope this answers your questions.
Vineeth
On Sat, Jun 6, 2020 at 3:13 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> Hi,
>
> 06/06/2020 21:43, Vineeth Thapeta:
> > Hi guys,
> >
> > I had to roll back OFED version from 5.0 to 4.4 because another library
> > Moongen has trouble building with OFED 5.0.
>
> How Moongen is related to OFED?
> Why using OFED and not upstream packaging of rdma-core?
> Which distribution are you using?
>
> > I rolled back the version and
> > Moongen builds and when I try to build dpdk 18.11, 19.11,17.11. All the
> > three builds fail with the following error (
> https://pastebin.com/fiw7iz1Z
> > Link of build error). Does anyone know why this happens.
>
> Any DPDK version should build with any version of OFED or rdma-core.
> Note: DPDK 17.11 is not supported anymore.
>
> > I am exhausted
> > with roll backs,if anyone can help me with this I would be grateful. , By
> > the looks of it, it might mean it had problems with the OFED driver? I
> > installed the MLNX ofed driver without any flags, i.e ./mlnxofedinstall.
> If
> > you want any further information,please let me know. Any suggestion would
> > be appreciated, even if you don't think it might work. I have been trying
> > to install these two for the past week, without much success. Are the
> above
> > mentioned DPDK version not compatible with said driver(4.4)?
>
> Let's focus on your goal and see what is the real issue you hit.
> Which version of DPDK do you need?
> Why not start with the latest LTS, which is 19.11?
>
>
>
--
Kind Regards,
Vineeth Sagar
CS Graduate Student
next prev parent reply other threads:[~2020-06-06 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 19:43 Vineeth Thapeta
2020-06-06 20:13 ` Thomas Monjalon
2020-06-06 20:54 ` Vineeth Thapeta [this message]
2020-06-06 21:55 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADWAvF7DRcgdC2P=CvyojoKQ5j=6BcLmkGjfZb4V5uBAPtTG4g@mail.gmail.com' \
--to=vthape2@uic.edu \
--cc=thomas@monjalon.net \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).