From: Stephen Hemminger <stephen@networkplumber.org>
To: "Rosen, Rami" <rami.rosen@intel.com>
Cc: Filip Janiszewski <contact@filipjaniszewski.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK device name
Date: Thu, 19 Apr 2018 09:24:20 -0700 [thread overview]
Message-ID: <20180419092420.759a3959@shemminger-XPS-13-9360> (raw)
In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F9531E4503@HASMSX110.ger.corp.intel.com>
On Thu, 19 Apr 2018 07:15:07 +0000
"Rosen, Rami" <rami.rosen@intel.com> wrote:
> Hi Flip,
> I assume that by "port numbers" you mean the PCI bus id (BDF)
> that is used by DPDK (for bind, for example).
>
> You can fetch the bus id for a netdevice named "eth0" by
> ethtool -i eth0 | grep bus-info
> bus-info: 0000:01:00.0
>
> If you mean the internal port number (starting from 0 for the first port, and so on) inside DPDK, then there is no
> mapping between the interface name (as seen by ifconfig) and the internal DPDK port number.
>
> Regards,
> Rami Rosen
>
>
>
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Filip Janiszewski
> Sent: Thursday, April 19, 2018 09:13
> To: users@dpdk.org
> Subject: [dpdk-users] DPDK device name
>
> Hi,
>
> Is there any mapping between the port names I see while using 'ifconfig'
> and the port numbers I use normally to handle NIC ports? In other words, is there a way to identify which ports number corresponds to a given linux interface name?
>
> Thanks
>
> --
> BR, Filip
> +48 666 369 823
Short answer No.
Long answer.
DPDK devices can be virtual, shared, or connected to a bus. Most devices are connected
to Pci bus and must be unbound and rebound to use DPDK userspace i/o. The PCI address
is the underlying value used by DPDK. You can find the value via sysfs
/sys/class/net/ethN/device (reliable) or ethtool (works for most devices). But once
device is unbound from the kernel driver, it no longer has a kernel assigned name.
DPDK port numbers are assigned in order, so if multiple devices are used by DPDK
they are seen in lexical order as PCI scanning occurs.
It is also possible to use KNI to get a kernel network interface for a DPDK
port.
Lots of options.
prev parent reply other threads:[~2018-04-19 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 6:12 Filip Janiszewski
2018-04-19 7:15 ` Rosen, Rami
2018-04-19 16:24 ` Stephen Hemminger [this message]
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=20180419092420.759a3959@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=contact@filipjaniszewski.com \
--cc=rami.rosen@intel.com \
--cc=users@dpdk.org \
/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).