DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shani Peretz <shperetz@nvidia.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [RFC PATCH 0/5] Introduce mempool object new debug capabilities
Date: Mon, 7 Jul 2025 05:46:36 +0000	[thread overview]
Message-ID: <SA1PR12MB94915F9CB104B4383F1AE01EBF4FA@SA1PR12MB9491.namprd12.prod.outlook.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9FD14@smartserver.smartshare.dk>



> -----Original Message-----
> From: Morten Brørup <mb@smartsharesystems.com>
> Sent: Thursday, 19 June 2025 15:57
> To: Stephen Hemminger <stephen@networkplumber.org>; Shani Peretz
> <shperetz@nvidia.com>
> Cc: dev@dpdk.org
> Subject: RE: [RFC PATCH 0/5] Introduce mempool object new debug
> capabilities
> 
> External email: Use caution opening links or attachments
> 
> 
> > From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> > Sent: Monday, 16 June 2025 17.30
> >
> > On Mon, 16 Jun 2025 10:29:05 +0300
> > Shani Peretz <shperetz@nvidia.com> wrote:
> >
> > > 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 (5):
> > >   mempool: record mempool objects operations history
> > >   drivers: add mempool history compilation flag
> > >   net/mlx5: mark an operation in mempool object's history
> > >   app/testpmd: add testpmd command to dump mempool history
> > >   usertool: add a script to parse mempool history dump
> > >
> >
> > Could this not already be done with tracing infrastructure?
> 
> I agree with Stephen on this.
> 
> And, if you plan to use this for performance measurements, you can use the
> coming PMU trace to trace the objects' movements between CPU caches and
> RAM, so you can discriminate between hot and cold objects.

We want to track when the transition of objects between the app and the PMD. So I don't know if PMU library is helpful in this case, isn't it?


  reply	other threads:[~2025-07-07  5:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  7:29 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 [this message]
2025-07-07  5:45   ` Shani Peretz
2025-07-07 12:10     ` Morten Brørup

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=SA1PR12MB94915F9CB104B4383F1AE01EBF4FA@SA1PR12MB9491.namprd12.prod.outlook.com \
    --to=shperetz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=stephen@networkplumber.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).