The patch allowing to retrieve the network interface index and name via Netlink: https://www.spinics.net/lists/linux-rdma/msg62948.html In Linux tree: 5b2cc79d (Leon Romanovsky 2018-03-27 20:40:49 +0300 270)
So, the problem depends on ib_core module version - 4.16 supports getting ifindex via Netlink, 4.15 does not. Mellanox OFED brings its own ib_core module, that's why it works over ancient 3.10.327. I'll update log message of my patch to describe the matter. With best regards, Slava > -----Original Message----- > From: Slava Ovsiienko > Sent: Friday, April 5, 2019 12:38 > To: 'David Christensen' <d...@linux.vnet.ibm.com>; dev@dpdk.org > Cc: Shahaf Shuler <shah...@mellanox.com>; Ali Alnubani > <alia...@mellanox.com> > Subject: RE: [dpdk-dev] [PATCH 1/1] net/mlx5: fix device probing for old > kernel drivers > > > -----Original Message----- > > From: David Christensen <d...@linux.vnet.ibm.com> > > Sent: Thursday, April 4, 2019 22:06 > > To: Slava Ovsiienko <viachesl...@mellanox.com>; dev@dpdk.org > > Cc: Shahaf Shuler <shah...@mellanox.com> > > Subject: Re: [dpdk-dev] [PATCH 1/1] net/mlx5: fix device probing for > > old kernel drivers > > > > > Retrieving network interface index via Netlink fails in case of old > > > mlx5 kernel drivers installed > >> Can you put a boundary on this statement with a kernel driver version? > > > > Dave > > As far as I know this setup experiences the problem (I debugged on): > 4.15.32+ > Ubuntu 16.04.5 LTS > mlx5_core 5.0-0 (from Linux Upstream) > standalone ConnextX-4LX virtual function > > These setups has no problem: > 3.10.0-327 > Red Hat7.2 > mlx5_core 4.6-0.2.0 (from OFED) > standalone ConnextX-4LX physical function > > 5.0rc7+ > Red Hat 7.5 > mlx5_core 5.0-0 > standalone ConnextX-4LX physical function > > I'll try to get more information regarding other problematic configs. > > Regards, > Slava
