From: <wang.yong19@zte.com.cn>
To: <rasland@mellanox.com>
Cc: <george.dit@gmail.com>, <nelio.laranjeiro@6wind.com>, <users@dpdk.org>
Subject: [dpdk-users] 答复: RE: Compile DPDK 17.11 with Mellanox NIC support
Date: Thu, 1 Mar 2018 21:44:59 +0800 (CST) [thread overview]
Message-ID: <201803012144591964424@zte.com.cn> (raw)
In-Reply-To: <AM4PR05MB16849BD11D501E446E13495EC2C60@AM4PR05MB1684.eurprd05.prod.outlook.com>
Thanks for your advice.
It worked after I add the "--upstream-libs" parameter.
I really appreciate your help.
Best regards,
Wang Yong
------------------oringin------------------
from:RaslanDarawsheh <rasland@mellanox.com>
to:汪勇10032886;george.dit@gmail.com <george.dit@gmail.com>
cc:Nélio Laranjeiro <nelio.laranjeiro@6wind.com>users@dpdk.org <users@dpdk.org>
date:2018年03月01日 21:25
subject:RE: [dpdk-users] Compile DPDK 17.11 with Mellanox NIC support
Hi,
I believe you are missing the --upstream-libs from OFED installation:
Try it as following:
./mlnxofedinstall --skip-distro-check --dpdk --add-kernel-support --upstream-libs /etc/init.d/openibd restart
Then rebuild your DPDK.
Kindest regards,
Raslan Darawsheh
-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of wang.yong19@zte.com.cn
Sent: Thursday, March 1, 2018 3:19 PM
To: george.dit@gmail.com
Cc: Nélio Laranjeiro <nelio.laranjeiro@6wind.com>; users@dpdk.org
Subject: Re: [dpdk-users] Compile DPDK 17.11 with Mellanox NIC support
Hi,
I met the same problem. My DPDK build environment is "CentOS7.0 + kernel 3.10.0-229.el7.x86_64".
I have download the OFED 4.2 and use the following command to install:
./mlnxofedinstall --skip-distro-check --dpdk --add-kernel-support /etc/init.d/openibd restart However, I still met error while I am compiling DPDK-17.11. The error information is :
In file included from /home/wangyong/dpdk-17.11/drivers/net/mlx4/mlx4.c:71:0:
/home/wangyong/dpdk-17.11/drivers/net/mlx4/mlx4_rxtx.h:44:31: fatal error: infiniband/mlx4dv.h: No such file or directory #include <infiniband/mlx4dv.h>
^
compilation terminated.
make[6]: *** [mlx4.o] Error 1
make[5]: *** [mlx4] Error 2
make[4]: *** [net] Error 2
make[3]: *** [drivers] Error 2
make[2]: *** [all] Error 2
make[1]: *** [pre_install] Error 2
make: *** [install] Error 2
I checked the "/usr/include/infiniband" directory and I couldn't find the mlx4dv.h file.
Are there any other configurations or steps required? Or the kernel version of linux can't be 3.10 ?
------------------origin------------------
from:george.dit@gmail.com <george.dit@gmail.com>
to:Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
cc:users@dpdk.org <users@dpdk.org>
date:2018年01月05日 16:03
subject:Re: [dpdk-users] Compile DPDK 17.11 with Mellanox NIC support Hi Nelio,
Thanks for the prompt reply and guidance!
My OFED version was 4.1, that's why I was unable to build DPDK 17.11.
With OFED 4.2 everything works on my kernel (v4.4)!
I have one more question: What is the suggested OFED version in order to have a fully featured NIC with all the DPDK classification/offloading capabilities?
My NICs are 100G ConnectX-4 (dual and single port).
Best regards,
Georgios
On Fri, Jan 5, 2018 at 8:46 AM, Nelio Laranjeiro <nelio.laranjeiro@6wind.com
> wrote:
> Hi George
>
> On Fri, Jan 05, 2018 at 08:38:11AM +0100, george.dit@gmail.com wrote:
> > Hi,
> >
> > I noticed that DPDK 17.11 brought some changes regarding the
> > Mellanox drivers, hence my compilation script does not work for this
> > version of
> DPDK.
> >
> > Specifically, the release notes of this version state:
> >
> > "Enabled the PMD to run on top of upstream Linux kernel and
> > rdma-core
> libs,
> > removing the dependency on specific Mellanox OFED libraries."
> >
> > Previously, I was setting CONFIG_RTE_LIBRTE_MLX5_PMD but now, with
> > this option set I get build errors in drivers/net/mlx5/mlx5.c.
> >
> > Could you please provide some guidance on how DPDK is expected to
> > work without OFED?
> > Is there any other configuration required?
>
> You should find anything useful in the NIC documentation [1], you have
> two possibilities, keep using the distribution and install MLNX_OFED
> 4.2, or update the Linux Kernel and use RDMA-Core, both are explained
> in he section "21.5.1. Installation".
>
> Regards,
>
> [1]
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdpd
> k.org%2Fdoc%2Fguides%2Fnics%2Fmlx5.html&data=02%7C01%7Crasland%40mella
> nox.com%7Cb975ffe6ec1e4dd22b4808d57f76feb3%7Ca652971c7d2e4d9ba6a4d1492
> 56f461b%7C0%7C0%7C636555071431060900&sdata=EOrSSjM9A7MsoWpvQOtW%2FzxnY
> wXaULG53hU%2BQjA4XK8%3D&reserved=0
>
> --
> Nélio Laranjeiro
> 6WIND
>
--
Georgios Katsikas
Industrial Ph.D. Student
Network Intelligence Group
Decision, Networks, and Analytics (DNA) Lab RISE SICS
E-Mail: georgios.katsikas@ri.se
prev parent reply other threads:[~2018-03-01 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 7:38 [dpdk-users] " george.dit
2018-01-05 7:46 ` Nelio Laranjeiro
2018-01-05 8:02 ` george.dit
2018-01-05 8:40 ` Nelio Laranjeiro
2018-01-05 8:43 ` george.dit
2018-01-08 2:38 ` Hui Ling
2018-01-08 5:00 ` george.dit
2018-03-01 13:18 ` wang.yong19
2018-03-01 13:25 ` Raslan Darawsheh
2018-03-01 13:44 ` wang.yong19 [this message]
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=201803012144591964424@zte.com.cn \
--to=wang.yong19@zte.com.cn \
--cc=george.dit@gmail.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=rasland@mellanox.com \
--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).