From: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: DPDK Netvsc - RNDIS reports VF but device not found, retrying
Date: Tue, 23 Jan 2024 21:06:22 +0200 [thread overview]
Message-ID: <CAAFk=6DhkkXC2i_jAnwTSv_OpsiO8dL-FswMx2w8b0qhgmvbXg@mail.gmail.com> (raw)
In-Reply-To: <20240123101343.08180392@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
No worries,
maybe you have a combination of VM type/kernel version/mlx5(or mlx4)
drivers that worked for you on Azure, just want to make dpdk work on Azure
in any capacity to begin with.
On Tue, Jan 23, 2024 at 8:13 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Tue, 23 Jan 2024 19:51:33 +0200
> Oleksandr Nahnybida <oleksandrn@interfacemasters.com> wrote:
>
> > azureuser@dpdk0:~$ ethtool -i enP47056s2
> > driver: mlx5_core
> > version: 5.15.0-1053-azure
> > firmware-version: 16.30.1284 (MSF0000000012)
> > expansion-rom-version:
> > bus-info: b7d0:00:02.0
> >
> > I also installed rdma-core/libibverbs1 (dpdk was compiled
> > with ibverbs_link=shared)
> >
> > azureuser@dpdk0:~$ apt-cache policy rdma-core
> > rdma-core:
> > Installed: 28.0-1ubuntu1
> > azureuser@dpdk0:~$ apt-cache policy libibverbs1
> > libibverbs1:
> > Installed: 28.0-1ubuntu1
>
> Sorry, my expertise on all the variations of mlx5 driver stuff is
> limited, and no longer have free access to Azure.
>
[-- Attachment #2: Type: text/html, Size: 1490 bytes --]
next prev parent reply other threads:[~2024-01-23 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 12:34 Oleksandr Nahnybida
2024-01-23 16:32 ` Stephen Hemminger
2024-01-23 17:51 ` Oleksandr Nahnybida
2024-01-23 18:13 ` Stephen Hemminger
2024-01-23 19:06 ` Oleksandr Nahnybida [this message]
2024-01-24 1:33 ` Stephen Hemminger
2024-01-25 11:36 ` Oleksandr Nahnybida
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='CAAFk=6DhkkXC2i_jAnwTSv_OpsiO8dL-FswMx2w8b0qhgmvbXg@mail.gmail.com' \
--to=oleksandrn@interfacemasters.com \
--cc=stephen@networkplumber.org \
--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).