From: Thomas Monjalon <thomas@monjalon.net>
To: "Benoit Ganne (bganne)" <bganne@cisco.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
users@dpdk.org, viacheslavo@mellanox.com, matan@mellanox.com,
rasland@mellanox.com, saeedm@mellanox.com, eranbe@mellanox.com,
markb@mellanox.com
Subject: Re: [dpdk-users] CX4-Lx VF link status in Azure
Date: Thu, 26 Mar 2020 19:52:27 +0100 [thread overview]
Message-ID: <9551713.0AQdONaE2F@xps> (raw)
In-Reply-To: <CH2PR11MB432798DF21D43DD7AAEFEEAFC1CF0@CH2PR11MB4327.namprd11.prod.outlook.com>
Pasting back this important info:
"
Note that ethtool and '/sys/class/net/<iface>/speed' also fails
to report the link speed (but not the link status).
"
26/03/2020 19:27, Benoit Ganne (bganne):
> Yes everything is initialized correctly. The netdev itself is configured and usable from Linux (ping etc.). Just removing the over-strict check in mlx5 PMD is enough for everything to work fine: https://gerrit.fd.io/r/c/vpp/+/26152/1/build/external/patches/dpdk_20.02/0002-mlx5-azure-workaround.patch
> The link speed is unknown but this is not issue, and link state and other link info are correctly reported.
> Thomas, any input regarding this behavior in mlx5 PMD?
I am not aware about the lack of link speed info.
It is probably not specific to ConnectX-4 Lx.
I guess it happens only with Hyper-V?
Cc mlx5 maintainers
next prev parent reply other threads:[~2020-03-26 18:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 19:07 Benoit Ganne (bganne)
2020-03-25 21:32 ` Stephen Hemminger
2020-03-25 22:48 ` Stephen Hemminger
2020-03-26 14:26 ` Benoit Ganne (bganne)
2020-03-26 17:57 ` Stephen Hemminger
2020-03-26 18:27 ` Benoit Ganne (bganne)
2020-03-26 18:52 ` Thomas Monjalon [this message]
2020-03-26 19:00 ` Benoit Ganne (bganne)
2020-03-26 20:09 ` Mark Bloch
2020-03-26 20:40 ` Thomas Monjalon
2020-03-26 21:31 ` Thomas Monjalon
2020-03-27 10:02 ` Benoit Ganne (bganne)
2020-03-27 10:13 ` Thomas Monjalon
2020-03-27 17:26 ` Benoit Ganne (bganne)
2020-03-27 22:34 ` Thomas Monjalon
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=9551713.0AQdONaE2F@xps \
--to=thomas@monjalon.net \
--cc=bganne@cisco.com \
--cc=eranbe@mellanox.com \
--cc=markb@mellanox.com \
--cc=matan@mellanox.com \
--cc=rasland@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=viacheslavo@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).