DPDK usage discussions
 help / color / Atom feed
From: Mark Bloch <markb@mellanox.com>
To: "Benoit Ganne (bganne)" <bganne@cisco.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	"users@dpdk.org" <users@dpdk.org>,
	"viacheslavo@mellanox.com" <viacheslavo@mellanox.com>,
	"matan@mellanox.com" <matan@mellanox.com>,
	"rasland@mellanox.com" <rasland@mellanox.com>,
	"saeedm@mellanox.com" <saeedm@mellanox.com>,
	"eranbe@mellanox.com" <eranbe@mellanox.com>
Subject: Re: [dpdk-users] CX4-Lx VF link status in Azure
Date: Thu, 26 Mar 2020 13:09:57 -0700
Message-ID: <4c84d14c-e12f-298b-474b-0c1da812a6d2@mellanox.com> (raw)
In-Reply-To: <CH2PR11MB4327F04EE3A646B7275F7D62C1CF0@CH2PR11MB4327.namprd11.prod.outlook.com>



On 3/26/2020 12:00, Benoit Ganne (bganne) wrote:
>> 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.fd.io%2Fr%2Fc%2Fvpp%2F%2B%2F26152%2F1%2Fbuild%2Fexternal%2Fpatches%2Fdpdk_20.02%2F0&amp;data=02%7C01%7Cmarkb%40mellanox.com%7Ccf7438ae7d924c03b03308d7d1b7fd83%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C637208460478847341&amp;sdata=fV4wrAvzmHNM88mfCr6lxFXG0ANVOP0rBjfovZii84c%3D&amp;reserved=0
>> 002-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?

Should be fixed by those 3 commits (last 1 one is just cosmetic):

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dc392fc56f39a00a46d6db2d150571ccafe99734
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=c268ca6087f553bfc0e16ffec412b983ffe32fd4
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=2f5438ca0ee01a1b3a9c37e3f33d47c8122afe74

Mark

> 
> For me there are 2 separate issues:
>  1) Linux kernel driver does not report link speed in Azure for CX4-Lx in Ubuntu 18.04
>  2) mlx5 PMD enforce that both link speed is defined and link is up to update interface state
> 
> If (1) is fixed, (2) should work, but to me (2) is too strict for no good reason: we do not really care about reported link speed, esp in a virtual environment it usually does not mean much, but we do care about link state.
> 
> ben
> 

  reply index

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
2020-03-26 19:00           ` Benoit Ganne (bganne)
2020-03-26 20:09             ` Mark Bloch [this message]
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 publically 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=4c84d14c-e12f-298b-474b-0c1da812a6d2@mellanox.com \
    --to=markb@mellanox.com \
    --cc=bganne@cisco.com \
    --cc=eranbe@mellanox.com \
    --cc=matan@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=saeedm@mellanox.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --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

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox