DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/4] app/dumpcap: assorted fixes
Date: Tue, 17 Nov 2026 08:06:18 -0800	[thread overview]
Message-ID: <20261117160727.388470-1-stephen@networkplumber.org> (raw)

Som patchs for 27.03.
These came out of benchmarking dumpcap: capture for 10 seconds, count
how many packets landed in the file. The numbers would not line up, and
the reasons turned out to be in the stop logic.

The last patch is unrelated cleanup from reading that code.
The error handling could call rte_exit before rte_eal_init was run.

All four are candidates for stable.

Stephen Hemminger (4):
  app/dumpcap: fix packet count overshoot
  app/dumpcap: fix capture duration
  app/dumpcap: fix pcap timestamps
  app/dumpcap: do not use rte_exit before EAL init

 app/dumpcap/main.c | 87 +++++++++++++++++++++++++++++++++---------------------
 1 file changed, 54 insertions(+), 33 deletions(-)

-- 
2.53.0

Stephen Hemminger (4):
  app/dumpcap: fix packet count overshoot
  app/dumpcap: fix capture duration
  app/dumpcap: fix pcap timestamps
  app/dumpcap: do not use rte_exit before EAL init

 app/dumpcap/main.c | 87 ++++++++++++++++++++++++++++------------------
 1 file changed, 54 insertions(+), 33 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-11-17 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 16:06 Stephen Hemminger [this message]
2026-11-17 16:06 ` [PATCH 1/4] app/dumpcap: fix packet count overshoot Stephen Hemminger
2026-11-17 16:06 ` [PATCH 2/4] app/dumpcap: fix capture duration Stephen Hemminger
2026-11-17 16:06 ` [PATCH 3/4] app/dumpcap: fix pcap timestamps Stephen Hemminger
2026-11-17 16:06 ` [PATCH 4/4] app/dumpcap: do not use rte_exit before EAL init Stephen Hemminger

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=20261117160727.388470-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --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