DPDK usage discussions
 help / color / mirror / Atom feed
From: fwefew 4t4tg <7532yahoo@gmail.com>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: users@dpdk.org
Subject: Re: If or how one gets an IP address associated with a vfio-pci bound NIC
Date: Wed, 3 Nov 2021 21:40:39 -0400	[thread overview]
Message-ID: <CA+Tq66WyUpjG-EME-A0FTGCfJdr_0QoyWZ3K3u2qbvh1-FMUag@mail.gmail.com> (raw)
In-Reply-To: <0aa050c0-fa95-a4cd-bb58-ba3dfef8146d@linux.vnet.ibm.com>

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

>
> David wrote:
> >I don't think you understand the intent behind the DPDK framework.
>
> Thank you. Indeed I stand corrected. Associating an IP address with the
DPDK NIC works from a bad frame on the problem.

I'd appreciate one additional bit of information if possible. Once the DPDK
NIC is bound to vfio-pci the DPDK Linux manual at
https://doc.dpdk.org/guides/linux_gsg/linux_drivers.html#vfio mentions
setup steps including:

Create the desired number of VF devices
echo 2 > /sys/bus/pci/devices/0000:86:00.0/sriov_numvfs

My question: what is the upper bound on the number of VF devices? What's
the thinking process? For example,
maybe one of these approaches makes sense?

- VF device count is bound from above by the number or RX/TX queues
- VF device count is bound from above by the amount of on-NIC memory
- VF device count is bound from above by manufacturer. Each NIC has some
max; read specs
- VF device count is like the number of ports on a UNIX: 1000s are
available and what you need depends on software: how many concurrent
connections are needed?

DPDK must have an API that programatically discovers the PFs and VFs per PF.

Finally: is a VF device duplex (sends and receives)? Or just RX or just TX
only?

Thank you.

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

  reply	other threads:[~2021-11-04  1:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 23:14 fwefew 4t4tg
2021-11-03 18:11 ` David Christensen
2021-11-04  1:40   ` fwefew 4t4tg [this message]
2021-11-04 17:14     ` David Christensen

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=CA+Tq66WyUpjG-EME-A0FTGCfJdr_0QoyWZ3K3u2qbvh1-FMUag@mail.gmail.com \
    --to=7532yahoo@gmail.com \
    --cc=drc@linux.vnet.ibm.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).