From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: David Christensen <drc@linux.vnet.ibm.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Shahaf Shuler <shahafs@mellanox.com>,
Ali Alnubani <alialnu@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH 1/1] net/mlx5: fix device probing for old kernel drivers
Date: Fri, 5 Apr 2019 12:49:42 +0000 [thread overview]
Message-ID: <AM4PR05MB3265666A1DFE68D370C2B98DD2510@AM4PR05MB3265.eurprd05.prod.outlook.com> (raw)
Message-ID: <20190405124942.sZq6EIqBvUOvVqI0YR8_kQK85cMYk5PiwNvl_5qX1NQ@z> (raw)
In-Reply-To: <AM4PR05MB3265B7B60C2E4D0981F297CFD2510@AM4PR05MB3265.eurprd05.prod.outlook.com>
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' <drc@linux.vnet.ibm.com>; dev@dpdk.org
> Cc: Shahaf Shuler <shahafs@mellanox.com>; Ali Alnubani
> <alialnu@mellanox.com>
> Subject: RE: [dpdk-dev] [PATCH 1/1] net/mlx5: fix device probing for old
> kernel drivers
>
> > -----Original Message-----
> > From: David Christensen <drc@linux.vnet.ibm.com>
> > Sent: Thursday, April 4, 2019 22:06
> > To: Slava Ovsiienko <viacheslavo@mellanox.com>; dev@dpdk.org
> > Cc: Shahaf Shuler <shahafs@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
next prev parent reply other threads:[~2019-04-05 12:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 14:14 Viacheslav Ovsiienko
2019-04-03 14:14 ` Viacheslav Ovsiienko
2019-04-04 19:06 ` David Christensen
2019-04-04 19:06 ` David Christensen
2019-04-05 9:37 ` Slava Ovsiienko
2019-04-05 9:37 ` Slava Ovsiienko
2019-04-05 12:49 ` Slava Ovsiienko [this message]
2019-04-05 12:49 ` Slava Ovsiienko
2019-04-05 13:25 ` [dpdk-dev] [PATCH v2 " Viacheslav Ovsiienko
2019-04-05 13:25 ` Viacheslav Ovsiienko
2019-04-08 6:00 ` Shahaf Shuler
2019-04-08 6:00 ` Shahaf Shuler
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=AM4PR05MB3265666A1DFE68D370C2B98DD2510@AM4PR05MB3265.eurprd05.prod.outlook.com \
--to=viacheslavo@mellanox.com \
--cc=alialnu@mellanox.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=shahafs@mellanox.com \
/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).