From: Shani Peretz <shperetz@nvidia.com>
To: <dev@dpdk.org>
Cc: <mb@smartsharesystems.com>, <stephen@networkplumber.org>,
<bruce.richardson@intel.com>, <ajit.khaparde@broadcom.com>,
<jerinj@marvell.com>, <konstantin.v.ananyev@yandex.ru>,
<david.marchand@redhat.com>, <maxime.coquelin@redhat.com>,
<gakhil@marvell.com>, <viacheslavo@nvidia.com>,
<thomas@monjalon.net>, "Shani Peretz" <shperetz@nvidia.com>
Subject: [PATCH v2 0/4] add mbuf debug capabilities
Date: Tue, 16 Sep 2025 18:12:03 +0300 [thread overview]
Message-ID: <20250916151207.556618-1-shperetz@nvidia.com> (raw)
In-Reply-To: <20250616072910.113042-1-shperetz@nvidia.com>
v2:
narrow scope to mbuf only - move the history tracking data to the rte_mbuf structure.
use a dynamic mbuf field to store the tracking bitmap.
remove the compilation flag.
v1:
This feature is designed to monitor the lifecycle of mempool objects
as they move between the application and the PMD.
It will allow us to track the operations and transitions of each mempool
object throughout the system, helping in debugging and understanding objects flow.
The implementation include several key components:
1. Added a bitmap to mempool's header (rte_mempool_objhdr)
that represent the operations history.
2. Added functions that allow marking operations on an
mempool objects.
3. Dumps the history to a file or the console
(rte_mempool_objects_dump).
4. Added python script that can parse, analyze the data and
present it in an human readable format.
5. Added compilation flag to enable the feature.
Shani Peretz (4):
mbuf: record mbuf operations history
net/mlx5: mark an operation in mbuf's history
app/testpmd: add testpmd command to dump mbuf history
usertool: add a script to parse mbuf history dump
app/test-pmd/cmdline.c | 60 ++++++++-
config/meson.build | 1 +
drivers/net/mlx5/mlx5_rx.c | 25 ++++
drivers/net/mlx5/mlx5_rx.h | 6 +
drivers/net/mlx5/mlx5_rxq.c | 15 ++-
drivers/net/mlx5/mlx5_rxtx_vec.c | 16 +++
drivers/net/mlx5/mlx5_tx.h | 21 +++
drivers/net/mlx5/mlx5_txq.c | 3 +
lib/ethdev/rte_ethdev.h | 15 +++
lib/mbuf/meson.build | 2 +
lib/mbuf/rte_mbuf.c | 10 +-
lib/mbuf/rte_mbuf.h | 23 +++-
lib/mbuf/rte_mbuf_dyn.h | 7 +
lib/mbuf/rte_mbuf_history.c | 181 ++++++++++++++++++++++++++
lib/mbuf/rte_mbuf_history.h | 154 ++++++++++++++++++++++
meson_options.txt | 2 +
usertools/dpdk-mbuf_history_parser.py | 173 ++++++++++++++++++++++++
17 files changed, 708 insertions(+), 6 deletions(-)
create mode 100644 lib/mbuf/rte_mbuf_history.c
create mode 100644 lib/mbuf/rte_mbuf_history.h
create mode 100755 usertools/dpdk-mbuf_history_parser.py
--
2.34.1
next prev parent reply other threads:[~2025-09-16 15:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 7:29 [RFC PATCH 0/5] Introduce mempool object new " Shani Peretz
2025-06-16 7:29 ` [RFC PATCH 1/5] mempool: record mempool objects operations history Shani Peretz
2025-06-16 7:29 ` [RFC PATCH 2/5] drivers: add mempool history compilation flag Shani Peretz
2025-06-16 7:29 ` [RFC PATCH 3/5] net/mlx5: mark an operation in mempool object's history Shani Peretz
2025-06-16 7:29 ` [RFC PATCH 4/5] app/testpmd: add testpmd command to dump mempool history Shani Peretz
2025-06-16 7:29 ` [RFC PATCH 5/5] usertool: add a script to parse mempool history dump Shani Peretz
2025-06-16 15:30 ` [RFC PATCH 0/5] Introduce mempool object new debug capabilities Stephen Hemminger
2025-06-19 12:57 ` Morten Brørup
2025-07-07 5:46 ` Shani Peretz
2025-07-07 5:45 ` Shani Peretz
2025-07-07 12:10 ` Morten Brørup
2025-07-19 14:39 ` Morten Brørup
2025-08-25 11:27 ` Slava Ovsiienko
2025-09-01 15:34 ` Morten Brørup
2025-09-16 15:12 ` Shani Peretz [this message]
2025-09-16 15:12 ` [PATCH v2 1/4] mbuf: record mbuf operations history Shani Peretz
2025-09-16 21:17 ` Stephen Hemminger
2025-09-16 21:33 ` Thomas Monjalon
2025-09-17 1:22 ` Morten Brørup
2025-09-16 15:12 ` [PATCH v2 2/4] net/mlx5: mark an operation in mbuf's history Shani Peretz
2025-09-16 21:14 ` Stephen Hemminger
2025-09-16 21:31 ` Thomas Monjalon
2025-09-16 15:12 ` [PATCH v2 3/4] app/testpmd: add testpmd command to dump mbuf history Shani Peretz
2025-09-16 15:12 ` [PATCH v2 4/4] usertool: add a script to parse mbuf history dump Shani Peretz
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=20250916151207.556618-1-shperetz@nvidia.com \
--to=shperetz@nvidia.com \
--cc=ajit.khaparde@broadcom.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=maxime.coquelin@redhat.com \
--cc=mb@smartsharesystems.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
/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).