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 09:40:05 +0100 [thread overview]
Message-ID: <20180105084005.4mbuv2ntopfi2wvb@laranjeiro-vm.dev.6wind.com> (raw)
In-Reply-To: <CAN9HtFAOd546zJWPG2ZTgWJiSWrj_8m9DaK=aE1AO6JBP9PQCQ@mail.gmail.com>
On Fri, Jan 05, 2018 at 09:02:54AM +0100, george.dit@gmail.com wrote:
> 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).
<snip/>
The one referenced in the documentation, you can still download and
install the latest GA from Mellanox website [1] (the link is also in the
documentation).
You can also take a look at features documentation page [2] on DPDK
documentation, those set to 'Y' are supported by the MLNX_OFED version
and (almost) by RDMA-Core.
Regards,
[1] http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers&ssn=l6arvsaqjfc9t768ll2nqa9dh3
[2] https://dpdk.org/doc/guides/nics/overview.html
--
Nélio Laranjeiro
6WIND
next prev parent reply other threads:[~2018-01-05 8:40 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
2018-01-05 8:02 ` george.dit
2018-01-05 8:40 ` Nelio Laranjeiro [this message]
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=20180105084005.4mbuv2ntopfi2wvb@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).