From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id ECBABA057C for ; Thu, 26 Mar 2020 21:40:16 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 57B294CA7; Thu, 26 Mar 2020 21:40:16 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 14358374C for ; Thu, 26 Mar 2020 21:40:15 +0100 (CET) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id A8F795C02A1; Thu, 26 Mar 2020 16:40:11 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Thu, 26 Mar 2020 16:40:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=uTWjjtea+evDRc7zJO+WPvZsgYE474y0FLuZ0xgyKlk=; b=HEJJAx2oZ5kZ Rl2j+Qh/p/RotpgkjT/EVq4cOQpbEJw3EFumYiqrv7ZztXizv8Tj/ShotAZMXNq0 2UUhrb1ts7+z1gbJfjmpJaL/vSEqevryOpHc+7HRl299XTJ1CPxzn+hduMNr5Qye E+6/4+8iKe3Nc/zHjyGgiSaq/07X420= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=uTWjjtea+evDRc7zJO+WPvZsgYE474y0FLuZ0xgyK lk=; b=vP3mRxAj1AKflZQ6jbyACQ5AuK3p8q7IQLofElnwXuCqCelOTvdsoJR+T X2kKNZwCevUEzvnWA7dssGzVjY4euNecF967dHc2XBiUFLVHyfchiUdZi1HF0Jh6 M5Ws02b+c9rVNQFRuRm6euYBWvsVA+bUQbO0vVObPrUU8nouZMyPtSq7fir5KzXD e+33LP/m/8TzrMZsnK6tLpiJxQVrTB9SMu8aWfSQbam13B21w/wpjjL7GXXQvsf6 QoyMhDeCHHhMvorqzUsZ+EYJPRweOlCRncF2cEzxA3rVTYrdPa09xkVrWy+q5+je 7OxQeRm7rgKt7+FA2UEPxAzDlLEhw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudehjedgjeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpehfugdrihhopdhkvghrnhgvlhdrohhrghenucfkphepjeejrddufeegrddv tdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id F0707306A3E2; Thu, 26 Mar 2020 16:40:08 -0400 (EDT) From: Thomas Monjalon To: "Benoit Ganne (bganne)" , Mark Bloch Cc: Stephen Hemminger , "users@dpdk.org" , "viacheslavo@mellanox.com" , "matan@mellanox.com" , "rasland@mellanox.com" , "saeedm@mellanox.com" , "eranbe@mellanox.com" Date: Thu, 26 Mar 2020 21:40:06 +0100 Message-ID: <1712113.QCnGb9OGeP@xps> In-Reply-To: <4c84d14c-e12f-298b-474b-0c1da812a6d2@mellanox.com> References: <4c84d14c-e12f-298b-474b-0c1da812a6d2@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-users] CX4-Lx VF link status in Azure X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" 26/03/2020 21:09, Mark Bloch: > > On 3/26/2020 12:00, Benoit Ganne (bganne) wrote: > >> Pasting back this important info: > >> " > >> Note that ethtool and '/sys/class/net//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? > > 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 Thanks for the patches 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 1 looks to be addressed with patches above. > > 2) mlx5 PMD enforce that both link speed is defined and link is up to update interface state Yes we can look at this issue. > > 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, I agree that link speed is less important than link status. > > esp in a virtual environment it usually does not mean much, Yes the link speed is shared between all VFs. > > but we do care about link state.