From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 0/8] Packet capture cleanup
Date: Thu, 14 Aug 2025 09:52:56 -0700 [thread overview]
Message-ID: <20250814165307.12786-1-stephen@networkplumber.org> (raw)
In-Reply-To: <20250811213632.16023-1-stephen@networkplumber.org>
This patch series addresses the problem of packet capture when
the secondary process is sending/receiving by using the same
mechanism as hot plug. It also fixes some bugs on shutdown
of dumpcap (and pdump).
The documentation has been updated and improved as well.
v2 - add documentation
Stephen Hemminger (8):
dumpcap: handle primary process exit
pdump: handle primary process exit
pdump: fix races in callbacks
dumpcap: handle pdump requests from primary
pdump: handle pdump requests from primary
pdump: forward callback enable to secondary
pdump: remove use of VLA
doc: update documentation on pdump library
app/dumpcap/main.c | 14 +
app/pdump/main.c | 16 +-
doc/guides/prog_guide/img/pdump_overview.svg | 135 +++++++++
doc/guides/prog_guide/pdump_lib.rst | 183 ++++++++-----
lib/pdump/meson.build | 2 -
lib/pdump/rte_pdump.c | 273 ++++++++++++++++---
6 files changed, 514 insertions(+), 109 deletions(-)
create mode 100644 doc/guides/prog_guide/img/pdump_overview.svg
--
2.47.2
next prev parent reply other threads:[~2025-08-14 16:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 21:34 [RFC 0/6] Packet capture fixes Stephen Hemminger
2025-08-11 21:34 ` [RFC 1/6] dumpcap: handle primary process exit Stephen Hemminger
2025-08-11 21:35 ` [RFC 2/6] pdump: " Stephen Hemminger
2025-08-11 21:35 ` [RFC 3/6] pdump: fix races in callbacks Stephen Hemminger
2025-08-11 21:35 ` [RFC 4/6] dumpcap: handle pdump requests from primary Stephen Hemminger
2025-08-11 21:35 ` [RFC 5/6] pdump: " Stephen Hemminger
2025-08-11 21:35 ` [RFC 6/6] pdump: forward callback enable to secondary Stephen Hemminger
2025-08-14 16:52 ` Stephen Hemminger [this message]
2025-08-14 16:52 ` [PATCH v2 1/8] dumpcap: handle primary process exit Stephen Hemminger
2025-08-14 16:52 ` [PATCH v2 2/8] pdump: " Stephen Hemminger
2025-08-14 16:52 ` [PATCH v2 3/8] pdump: fix races in callbacks Stephen Hemminger
2025-08-14 16:53 ` [PATCH v2 4/8] dumpcap: handle pdump requests from primary Stephen Hemminger
2025-08-14 16:53 ` [PATCH v2 5/8] pdump: " Stephen Hemminger
2025-08-14 16:53 ` [PATCH v2 6/8] pdump: forward callback enable to secondary Stephen Hemminger
2025-08-14 16:53 ` [PATCH v2 7/8] pdump: remove use of VLA Stephen Hemminger
2025-08-14 16:53 ` [PATCH v2 8/8] doc: update documentation on pdump library 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=20250814165307.12786-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;
as well as URLs for NNTP newsgroup(s).