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 2EB53A00C5; Thu, 7 May 2020 12:31:18 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7B4571DBA5; Thu, 7 May 2020 12:31:17 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id C35CF1DBA2 for ; Thu, 7 May 2020 12:31:16 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 1D4E05C0150; Thu, 7 May 2020 06:31:16 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Thu, 07 May 2020 06:31:16 -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=fm1; bh= 0SEM1QGIaT0D2vnDe9Erh07GRJ2IcbH+T01nivCCKO8=; b=bHQeChZoyE45juUr HLrJ4ZN9kHepqLa1br+MtWRoydcIXW4hERPEOPpyxB0CplLjZTmCOlf8yQMmSb6E eP0SBZSEK2R1yjcZ0fI9oluIu2MuVyzuHnkQg3HIZQY+HpPZiXBLoJ3W2RYw5vrb MQnUr5DAgh7DIy4tXPMeTX7rZa8lsnGU8zG1Zh2X0/8gopx77wrbuaqRVz9uqEbY ukGCIZx/r2CHVCzseBRwi1BdafrXKMABPmx/Uh5/w/GFgKF5lGZfI59IWVcHQx6P GdKIge4muRXr3tXGD1WXCq4N1my3wHKk//4H61ZqX6SdX0uLLn3zp19PGGTRtKs+ 7eGgVg== 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=0SEM1QGIaT0D2vnDe9Erh07GRJ2IcbH+T01nivCCK O8=; b=vss8gm9Rx7WA1KcoPitqQyDHupnPXWXXEfPuFHr3dDtDODVJ/ozLRg4CU FCwpryHi9doDxl6BObq2H1O7Osj0tD2ByvY0xrznrA/8L77xcHneuTNOXmL9Di28 ETBp7mSbJ1fmkw6JaO8zCRHsiJxR+Y76td3vC5pNLS4FvNiz+mpoHeq32lfPCqB8 rJB3sTHVfq4lQDDzZxSVnDdZbeKgm18lcn4T8N88M4va/Si1+KMby68eSFkKllZG CF0uMPDgA5hAYLvh5FkhXwZ4l+faT9HkhuiPS9DufXTjkpihLxVnJ6dxNVFNBTfp LkYWHmCKyhUf4VPbPs3iIXLenBnfw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrkedtgddvjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeekteehtdeivefhieegjeelgedufeejheekkeetueevieeuvdevuedt jeevheevteenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth 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 EF83E3066108; Thu, 7 May 2020 06:31:14 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit , Ivan Dyukov Cc: dev@dpdk.org, v.kuramshin@samsung.com, david.marchand@redhat.com, arybchenko@solarflare.com, matan@mellanox.com Date: Thu, 07 May 2020 12:31:14 +0200 Message-ID: <19616537.0c2gjJ1VT2@thomas> In-Reply-To: References: <4816966.qqrk5fENW1@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v1 0/6] ethdev: allow unknown link speed X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 07/05/2020 10:53, Ivan Dyukov: > 06.05.2020 20:42, Ferruh Yigit =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > On 4/27/2020 10:57 AM, Ivan Dyukov wrote: > >> This is initial patchset which introduces UNKNOWN speed to dpdk > >> applications. Also it contains changes related to printf formating. > >> Patchset contains changes for app/ and doc/ folders. > >> examples/ folder will be provided later. > >> > >> > > Also I can see there are some physical PMDs that are using 'ETH_SPEED_N= UM_NONE' > > as unknown, can we fix them as part of this set? > > > Initially, we had a plan to use UNKNOWN only for virtual devices. >=20 > Thomas, could you please comment this? No I think UNKNOWN must be used also for HW devices which are not able to provide a speed value. In mlx5 case, it can be used to return the link status (up/down) even if speed query is failing (it happens with buggy kernel version).