DPDK usage discussions
 help / color / mirror / Atom feed
From: Mikael R Carlsson <Mikael.R.Carlsson@tietoevry.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: DPDK port concept in rte_eth_dev
Date: Wed, 17 Aug 2022 11:28:20 +0000	[thread overview]
Message-ID: <DU0PR04MB922682CEFBDB881F2F81AF43A66A9@DU0PR04MB9226.eurprd04.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

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


[-- Attachment #2: Type: text/html, Size: 2734 bytes --]

             reply	other threads:[~2022-08-17 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 11:28 Mikael R Carlsson [this message]
2022-08-17 15:30 ` Stephen Hemminger

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=DU0PR04MB922682CEFBDB881F2F81AF43A66A9@DU0PR04MB9226.eurprd04.prod.outlook.com \
    --to=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).