From: Stephen Hemminger <stephen@networkplumber.org>
To: Mikael R Carlsson <Mikael.R.Carlsson@tietoevry.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: DPDK port concept in rte_eth_dev
Date: Wed, 17 Aug 2022 08:30:21 -0700 [thread overview]
Message-ID: <20220817083021.20459558@hermes.local> (raw)
In-Reply-To: <DU0PR04MB922682CEFBDB881F2F81AF43A66A9@DU0PR04MB9226.eurprd04.prod.outlook.com>
On Wed, 17 Aug 2022 11:28:20 +0000
Mikael R Carlsson <Mikael.R.Carlsson@tietoevry.com> wrote:
> Hi!
>
> Sorry for asking such a basic question but I have a hard time understanding the "port" concept in rte_eth_dev.
>
> I am using 2 VFs on the same physical port on a NIC, VF7 and VF6. These to VFs have there own unique PCI address. When I call rte_eth_dev_get_port_by_name, I suspect that I get the same port id from both PCI addresses (not sure here, still looking into this)
>
> Could someone please give me a short explanation of the "port" concept in rte_eth_dev, and how that correlates to PCI address and also eth_dev_rx_burst assuming you want to poll only from VF7 for example.
>
> Thanks in advance!
>
> / Mikael
>
DPDK ethdev port is more of an object index (like Linux file handle).
It can refer to many different types of devices.
prev parent reply other threads:[~2022-08-17 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 11:28 Mikael R Carlsson
2022-08-17 15:30 ` 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=20220817083021.20459558@hermes.local \
--to=stephen@networkplumber.org \
--cc=Mikael.R.Carlsson@tietoevry.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).