From: Olga Shern <olgas@mellanox.com>
To: Ananda Sathyanarayana <ananda@versa-networks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Mellanox external dependencies...
Date: Sat, 22 Apr 2017 15:13:41 +0000 [thread overview]
Message-ID: <DB6PR0501MB27574CA650B2744DC7B7AB51D31D0@DB6PR0501MB2757.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <13fc1cd878c09634db25d46635361b41@mail.gmail.com>
Hi Ananda,
>
> The following link has support for DPDK 16.11 and DPDK 2.2.
>
> http://www.mellanox.com/page/products_dyn?product_family=209&mtag=
> pmd_for_dpdk
>
[Olga] This link is for MLNX_DPDK releases that Mellanox maintains on top of dpdk.org versions
We support any version that is released on dpdk.org
>
>
> I did not find the mellonox drivers compatible for DPDK 16.04. Could you
> please point me to the right version of libibverbs, libmlx4 and Kernel modules
> (mlx4_core, mlx4_en, mlx4_ib and ib_uverbs) that can be used with DPDK
> 16.04.
>
[Olga] The instructions for latest DPDK version that was released (17.02) you can find here:
http://dpdk.org/doc/guides/nics/mlx4.html
for 16.04:
http://dpdk.org/doc/guides-16.04/nics/mlx4.html
We didn’t test 16.04 with latest MLNX_OFED that was released, but for mlx4 there should not be any problem with it.
http://www.mellanox.com/page/software_overview_ib
Let me know if you have any issue.
By the way, what is the reason using 16.04?
16.11 is LTS version in the community, any chance you can use it?
Best Regards,
Olga
________________________________________________________________
Olga Shern
SW Director DPDK
Mellanox Technologies, Raanana Israel
prev parent reply other threads:[~2017-04-22 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 18:20 Ananda Sathyanarayana
2017-04-22 15:13 ` Olga Shern [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=DB6PR0501MB27574CA650B2744DC7B7AB51D31D0@DB6PR0501MB2757.eurprd05.prod.outlook.com \
--to=olgas@mellanox.com \
--cc=ananda@versa-networks.com \
--cc=dev@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).