From: Stephen Hemminger <stephen@networkplumber.org>
To: Georgia Panoutsakopoulou <gpanoutsak@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Trouble locating functionality in code
Date: Fri, 12 Jun 2020 08:01:54 -0700 [thread overview]
Message-ID: <20200612080154.4c0a40f5@hermes.lan> (raw)
In-Reply-To: <CAG2+9UH1BbBeNdqqUuRzfFs-0PytSTJySxn9qvw3WvdxYuD_kg@mail.gmail.com>
On Fri, 12 Jun 2020 17:47:47 +0300
Georgia Panoutsakopoulou <gpanoutsak@gmail.com> wrote:
> Hi all,
> I'm having trouble locating the part of code that associates a network card
> with the dpdk internally used port id.
>
> For example, when I bind two ports with pci slots 0000:86:00.0
> and 0000:86:00.1 to dpdk driver igb_uio , how does dpdk populate this
> information and give a port id in each port? Is there a way to know this
> association without accessing dpdk structs by using functions like
> rte_eth_dev_get_name_by_port(portid,
> name)?
>
> I'm using dpdk app l2fwd and dpdk version 19.11.
>
> Thanks,
> Georgia
It is done by the PCI probing code that does a walk of sysfs.
prev parent reply other threads:[~2020-06-12 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 14:47 Georgia Panoutsakopoulou
2020-06-12 15:01 ` 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=20200612080154.4c0a40f5@hermes.lan \
--to=stephen@networkplumber.org \
--cc=gpanoutsak@gmail.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).