DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ivan Malov <ivan.malov@arknetworks.am>
Cc: dev@dpdk.org, Andrei Izrailev <Andrei.Izrailev@arknetworks.am>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: Re: Getting network port ID by ethdev port ID
Date: Mon, 05 Jun 2023 15:40:57 +0200	[thread overview]
Message-ID: <5020360.e8TTKsaY2g@thomas> (raw)
In-Reply-To: <f1a0b55-8977-23b6-3b3d-128c56ab629d@arknetworks.am>

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/<iface>/phys_port_name
> > /sys/class/net/<iface>/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.




  reply	other threads:[~2023-06-05 13:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 13:09 Ivan Malov
2023-06-05 13:40 ` Thomas Monjalon [this message]
2023-06-05 14:03   ` Ivan Malov
2023-06-05 14:10     ` Thomas Monjalon
2023-06-05 14:17       ` Ivan Malov
2023-06-05 14:29       ` Ivan Malov
2023-06-05 16:03         ` Thomas Monjalon
2023-06-05 18:50           ` Stephen Hemminger
2023-06-05 20:30             ` Ivan Malov
2023-06-05 22:39               ` Stephen Hemminger
2023-06-06  7:16                 ` Ivan Malov
2023-06-06 15:32                   ` Stephen Hemminger
2023-06-06  8:41               ` Ferruh Yigit

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=5020360.e8TTKsaY2g@thomas \
    --to=thomas@monjalon.net \
    --cc=Andrei.Izrailev@arknetworks.am \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=ivan.malov@arknetworks.am \
    /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).