From: Olga Shern <olgas@mellanox.com>
To: Richard Nutman <Richard.Nutman@s-a-m.com>,
"users@dpdk.org" <users@dpdk.org>
Cc: Erez Ferber <erezf@mellanox.com>
Subject: Re: [dpdk-users] mlx5 fails to probe on 16.11.5
Date: Fri, 16 Mar 2018 20:21:44 +0000 [thread overview]
Message-ID: <AM6PR0502MB3637A51184AE27EA6967993CD3D70@AM6PR0502MB3637.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <733AB18813E3864094592CC5191B172A235BBFE4@EX-UKHA-01.ad.s-a-m.com>
Hi Richard,
mlx5 PMD is not compiled by default in dpdk.org versions due to OFED dependency you need to enable it compilation in configure file.
Regarding:
>Also in mlx5_ethdev.c -> mlx5_dev_infos_get()
>info->flow_type_rss_offloads = ~MLX5_RSS_HF_MASK;
>was added as part of the .5 release, but the mask is undefined and fails to build.
Will check it
Best Regards,
Olga
-------------------------------------------------------
Olga Shern
SW Director DPDK
Mellanox Technologies, Raanana, Israel
-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of Richard Nutman
Sent: Friday, March 16, 2018 5:15 PM
To: users@dpdk.org
Subject: [dpdk-users] mlx5 fails to probe on 16.11.5
Hi all,
I tried switching from the Mellanox 16.11.4 release to the official DPDK LTS 16.11.5, but having issues getting it to work.
rte_eth_dev_count() returns 0, as mlx5_pci_probe() is never called from rte_eal_pci_probe_one_driver().
Anyone any idea what that would be ? Works fine in previous Mellanox releases.
Using Centos 7.2, Ofed 4.2-1.
Also in mlx5_ethdev.c -> mlx5_dev_infos_get()
info->flow_type_rss_offloads = ~MLX5_RSS_HF_MASK;
was added as part of the .5 release, but the mask is undefined and fails to build.
Thanks,
Richard Nutman
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mimecast.com&data=02%7C01%7Colgas%40mellanox.com%7C7fc66f1dd7d74bd6156508d58b50b718%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636568101152961423&sdata=a4rC2jHinSvgbxpXhqvl75AREYebFig95oZrL1uiBNM%3D&reserved=0
---------------------------------------------------------------------------------------
next prev parent reply other threads:[~2018-03-16 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 15:14 Richard Nutman
2018-03-16 20:21 ` Olga Shern [this message]
2018-03-19 10:49 ` Richard Nutman
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=AM6PR0502MB3637A51184AE27EA6967993CD3D70@AM6PR0502MB3637.eurprd05.prod.outlook.com \
--to=olgas@mellanox.com \
--cc=Richard.Nutman@s-a-m.com \
--cc=erezf@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).