From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4931342BBB; Mon, 5 Jun 2023 15:41:02 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 384DB4021F; Mon, 5 Jun 2023 15:41:02 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 8FA134003C for ; Mon, 5 Jun 2023 15:41:01 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id CD9C55C017F; Mon, 5 Jun 2023 09:41:00 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Mon, 05 Jun 2023 09:41:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1685972460; x=1686058860; bh=F0mjEJKufWwHlOiRdIJTDU3l1tTwBowaMuB ETe9TyBE=; b=MRSVQXGravGrKOe4FyGQV5+Fw+fJzTZcDK6v8r1sQT7sl2I5gY/ VekNZwJioLPqqX5aNNQdm2csiG30a88rJBK2EAyDyywQ8+rnzMpRg76wUswUxk3A RW5JxHaybesRjtOtEIHn0GCdxLzo72pHGSo2a3+OJvhyVZh0lQf5f9vz2sQ7cmo2 42Dwb3WuAXlT7fyZxCpTewXSOXfoBWAz9MHVLfj1b/Dt6/PBp8ardZo2G8rULJno fX+Unj53XMkp1R8r2jMNmaLgHv8BSZNCtNFezC14xQoRjq64Uk9rNuW3b35iBK3e hUluCvEsG3mk8EGiedXtAfZUJ6dO3yZDf4Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1685972460; x=1686058860; bh=F0mjEJKufWwHlOiRdIJTDU3l1tTwBowaMuB ETe9TyBE=; b=noyPQJPtNFylf4kMBq8tp2M8onK1CgZ19DSXFFKbOC00ZeEbpM6 mDUoEuSu3MHg+CMdpBNaYLtBUozW5SW5puEU+rNpil3wvbXQpUDYXjG//hbM4Wwy A34vB3XDp7LfQRwCuK6fm9ogX3ZlRNQfTNL8ftyLIZMbfVAv9S7L6HD+c0lHPYkc X8FhHUNrA7G99uRCGUO81RArnyoeKSsLFEuPKqPqGh7b1OZVw4cvfsSOqIm03KqJ esXSHAREW2miQqGViUoPdYtt3fAAKxjI8fNPZNOKF7lDW9gU0/1ULMOCxnfPLRGY nmmR2U371WTTiRsKCzvK8xhsFzAICctoc8Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeelledgieekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 5 Jun 2023 09:40:59 -0400 (EDT) From: Thomas Monjalon To: Ivan Malov Cc: dev@dpdk.org, Andrei Izrailev , Ferruh Yigit Subject: Re: Getting network port ID by ethdev port ID Date: Mon, 05 Jun 2023 15:40:57 +0200 Message-ID: <5020360.e8TTKsaY2g@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hello, 05/06/2023 15:09, Ivan Malov: > Dear community, > > Is there any means in DPDK to discover relationship between > network/physical ports of the given adapter/board and > etdevs deployed in DPDK application on top of it? > > For example, in Linux, there are facilities like > > > /sys/class/net//phys_port_name > > /sys/class/net//dev_port > > and > > > devlink port show > > Do we have something similar in DPDK? We can get the device name of a port: rte_eth_dev_get_name_by_port() > If no, would the feature be worthwhile implementing? We may have discrepancies in different device classes. Feel free to make a global status of device names.