test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Gokul K R (MS/ETA7-ETAS)" <KR.Gokul@in.bosch.com>
To: "jonathan.ribas@fraudbuster.mobi" <jonathan.ribas@fraudbuster.mobi>
Cc: "Nivethitha N Shanmugasundaram (ETAS-ICA/XPC-Fe6)"
	<NShanmugasundaram.Nivethitha@etas.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Subject: DPDK-Burst Replay Execution – NUMA Warning and No Frame Transmission Observed
Date: Wed, 16 Jul 2025 07:19:47 +0000	[thread overview]
Message-ID: <PAVPR10MB73553E56C6A7D42A2CE634E5A456A@PAVPR10MB7355.EURPRD10.PROD.OUTLOOK.COM> (raw)

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

Hi Jonathan 😊,
During the execution of the dpdk-replay tool, we encountered the following message:
port 0 is not on the good numa id (-1)
This appears to be an informational warning, typically generated when DPDK cannot determine the NUMA node for the PCI device. According to discussions on the DPDK stable mailing list, this warning is benign and does not affect functionality or performance—especially for NICs like Intel I225/I210 that do not report NUMA affinity.
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.
Observation:
Despite successful file reading and replay initiation, we did not observe any frames being transmitted or received on either the sender or the receiver side.
Could you please advise if there are any additional steps or configurations we should verify?

Best regards,
Gokul K R


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

                 reply	other threads:[~2025-07-17  8:27 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=PAVPR10MB73553E56C6A7D42A2CE634E5A456A@PAVPR10MB7355.EURPRD10.PROD.OUTLOOK.COM \
    --to=kr.gokul@in.bosch.com \
    --cc=NShanmugasundaram.Nivethitha@etas.com \
    --cc=dts@dpdk.org \
    --cc=jonathan.ribas@fraudbuster.mobi \
    /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).