DPDK patches and discussions
 help / color / mirror / Atom feed
From: spyroot <spyroot@gmail.com>
To: dev@dpdk.org
Subject: 810 VFIO , SRIOV, multi-process stats read DPDK testpmd.
Date: Mon, 14 Apr 2025 19:21:57 +0400	[thread overview]
Message-ID: <CABsV3rARRuh8Qhm4q+QCDAEmA8WP+6QK241ik4qoLyGJBPFdHg@mail.gmail.com> (raw)

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

Hi Folks,

I'm observing some unexpected behavior related to how statistics are
retrieved from a Physical Function (PF) on an Intel 810 NIC.

*Scenario:* I have two dpdk-testpmd instances running in separate
Kubernetes pods (same worker node). Each instance uses the -a flag to bind
to a different VF. (i.e to have consistent port id 0)

*Questions:*

   1.

   *PF Statistics and 64B Line Rate:*
   I'm noticing that the RX packet-per-second value reported on the PF side
   for a given VF is *higher than the theoretical maximum* for 64-byte
   packets.
   -

      Does the Intel 810 PMD apply any kind of optimization, offloading, or
      fast path processing when two VFs (e.g., A and B) are on the same PF?
      2.

   *Concurrent Stats Polling:*
   -

      When two separate dpdk-testpmd processes are running (in pod A and
      pod B), does the PMD or driver layer support concurrent reading of PF
      statistics?
      -

      Is there any locking or synchronization mechanism involved when
      multiple testpmd instances attempt to pull stats from the same PF
      simultaneously? ( in essence, does a firmware/OF support
concurrent read).

Thank you,

cd /usr/local/bin && dpdk-testpmd \
  --main-lcore \$main -l \$cores -n 4 \
  --socket-mem 2048 \
  --proc-type auto --file-prefix testpmd_rx0 \
  -a \$PCIDEVICE_INTEL_COM_DPDK \
  -- --forward-mode=rxonly --auto-start --stats-period 1'"

cd /usr/local/bin && dpdk-testpmd \
  --main-lcore \$main -l \$cores -n 4 \
  --socket-mem 2048 \
  --proc-type auto --file-prefix testpmd_rx1 \
  -a \$PCIDEVICE_INTEL_COM_DPDK \
  -- --forward-mode=rxonly --auto-start --stats-period 1'"

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

                 reply	other threads:[~2025-04-14 15:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CABsV3rARRuh8Qhm4q+QCDAEmA8WP+6QK241ik4qoLyGJBPFdHg@mail.gmail.com \
    --to=spyroot@gmail.com \
    --cc=dev@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).