From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
To: george.dit@gmail.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Compile DPDK 17.11 with Mellanox NIC support
Date: Fri, 5 Jan 2018 08:46:22 +0100 [thread overview]
Message-ID: <20180105074622.liwtcoadktbhj7e3@laranjeiro-vm.dev.6wind.com> (raw)
In-Reply-To: <CAN9HtFB_NZv88sCULh8YOtAqSUJVXfOJdgOMH4gYzEoymap=7g@mail.gmail.com>
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://dpdk.org/doc/guides/nics/mlx5.html
--
Nélio Laranjeiro
6WIND
next prev parent reply other threads:[~2018-01-05 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 7:38 george.dit
2018-01-05 7:46 ` Nelio Laranjeiro [this message]
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 ` [dpdk-users] 答复: " wang.yong19
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=20180105074622.liwtcoadktbhj7e3@laranjeiro-vm.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=george.dit@gmail.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).