From: Stephen Hemminger <stephen@networkplumber.org>
To: Ivan Malov <ivan.malov@arknetworks.am>
Cc: Ernesto Ruffini <eruffini@outsys.org>,
"'Gokul K R (MS/ETA7-ETAS)'" <KR.Gokul@in.bosch.com>,
users@dpdk.org, dev@dpdk.org,
"'Nivethitha N Shanmugasundaram (ETAS-ICA/XPC-Fe6)'"
<NShanmugasundaram.Nivethitha@etas.com>,
"'Aloysius Nishanth Britto (MS/ETA7-ETAS)'"
<Britto.AloysiusNishanth@in.bosch.com>
Subject: Re: Issue with DPDK-Burst Replay – No Frame Transmission Observed Despite Successful Replay
Date: Wed, 8 Apr 2026 09:37:52 -0700 [thread overview]
Message-ID: <20260408093752.109d2a61@phoenix.local> (raw)
In-Reply-To: <3183bfe9-1133-58e7-1387-88b85cb8e623@arknetworks.am>
On Fri, 25 Jul 2025 14:39:49 +0400 (+04)
Ivan Malov <ivan.malov@arknetworks.am> wrote:
> Hi Ernesto,
>
> On Fri, 25 Jul 2025, Ernesto Ruffini wrote:
>
> > Hi,
> > Did you try using usertools/dpdk-telemetry.py?
> > It attaches to a running DPDK process (so your sending process should stay running and not close immediately), and can show many counters, including packets output by a device.
> > At the command prompt, you can type "/ethdev/stats,0" and it will show all input and output packet counters for each configured queue in device 0.
> >
> > https://doc.dpdk.org/guides/howto/telemetry.html
>
> Thanks, that may indeed be helpful. But even without a secondary process, just
> inserting one invocation of statistics API and a printout to the port stop
> sequence of the target application would suffice to show the drops (if any).
>
> Thank you.
The DPDK dumpcap tool also adds statistics at end of capture into the pcapng format file.
prev parent reply other threads:[~2026-04-08 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 5:10 Issue with DPDK-Burst Replay – No Frame Transmission Observed Despite Successful Replay Gokul K R (MS/ETA7-ETAS)
2025-07-18 11:58 ` Ivan Malov
2025-07-23 5:35 ` Gokul K R (MS/ETA7-ETAS)
2025-07-23 5:58 ` Ivan Malov
2025-07-23 6:12 ` Ivan Malov
2025-07-24 10:08 ` Gokul K R (MS/ETA7-ETAS)
2025-07-24 10:24 ` Ivan Malov
2025-07-24 15:49 ` Gokul K R (MS/ETA7-ETAS)
2025-07-24 16:35 ` Ivan Malov
2025-07-25 6:32 ` Gokul K R (MS/ETA7-ETAS)
2025-07-25 6:46 ` Ivan Malov
2025-07-25 9:25 ` Ernesto Ruffini
2025-07-25 10:39 ` Ivan Malov
2026-04-08 16:37 ` Stephen Hemminger [this message]
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=20260408093752.109d2a61@phoenix.local \
--to=stephen@networkplumber.org \
--cc=Britto.AloysiusNishanth@in.bosch.com \
--cc=KR.Gokul@in.bosch.com \
--cc=NShanmugasundaram.Nivethitha@etas.com \
--cc=dev@dpdk.org \
--cc=eruffini@outsys.org \
--cc=ivan.malov@arknetworks.am \
--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