DPDK usage discussions
 help / color / mirror / Atom feed
From: "Gokul K R (MS/ETA7-ETAS)" <KR.Gokul@in.bosch.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Issue with DPDK-Burst Replay – No Frame Transmission Observed Despite Successful Replay
Date: Fri, 18 Jul 2025 05:10:38 +0000	[thread overview]
Message-ID: <PAVPR10MB73554B90C65B0D9A83AD8582A450A@PAVPR10MB7355.EURPRD10.PROD.OUTLOOK.COM> (raw)

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

Hi Team,
I’m currently working with the dpdk-burst-replay tool and encountered an issue during execution. Below are the details:
________________________________
Observation:
During replay, we received the following informational message:
port 0 is not on the good numa id (-1)
As per the DPDK mailing list discussions, this warning is typically benign—often seen on NICs like Intel I225/I210, which do not report NUMA affinity. Hence, we proceeded with execution.
________________________________
Command Used:
sudo numactl --cpunodebind=0 --membind=0 ./src/dpdk-replay Original_MAC.pcap 0000:01:00.1
Execution Output:
preloading Original_MAC.pcap file (of size: 143959 bytes)
file read at 100.00%
read 675 pkts (for a total of 143959 bytes). max packet length = 1518 bytes.
-> Needed MBUF size: 1648
-> Needed number of MBUFs: 675
-> Needed Memory = 1.061 MB
-> Needed Hugepages of 1 GB = 1
-> Needed CPUs: 1
-> Create mempool of 675 mbufs of 1648 octets.
-> Will cache 675 pkts on 1 caches.
________________________________
Issue:
Despite successful parsing of the pcap file and proper initialization, no frames were transmitted or received on either the sender or receiver sides.
________________________________
Environment Details:

  *   NIC used: Intel I225/I210
  *   Hugepages configured: 1 GB
  *   NUMA binding: --cpunodebind=0 --membind=0
  *   OS: [Your Linux distribution, e.g., Ubuntu 20.04]
  *   DPDK version: [Mention if known]

________________________________
Could you please advise if any additional setup, configuration, or known limitations may be impacting the packet transmission?
Thank you in advance for your support!


Best regards,
Gokul K R


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

             reply	other threads:[~2025-07-18  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  5:10 Gokul K R (MS/ETA7-ETAS) [this message]
2025-07-18 11:58 ` Ivan Malov

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=PAVPR10MB73554B90C65B0D9A83AD8582A450A@PAVPR10MB7355.EURPRD10.PROD.OUTLOOK.COM \
    --to=kr.gokul@in.bosch.com \
    --cc=dev@dpdk.org \
    --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).