DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Gagandeep Singh <g.singh@nxp.com>
Cc: dev@dpdk.org
Subject: Re: [v2 0/2] proc-info memory dump enhancement
Date: Fri, 11 Oct 2024 15:15:19 +0200	[thread overview]
Message-ID: <CAJFAV8w9FavCJx8CF9-EsvqjPyciTzKxsQFH-8Ne3bSzF+p4tw@mail.gmail.com> (raw)
In-Reply-To: <20240730110313.2555473-1-g.singh@nxp.com>

On Tue, Jul 30, 2024 at 2:04 PM Gagandeep Singh <g.singh@nxp.com> wrote:
>
> v2 change:
> * Handled a comment to add "MALLOC" while dumping
>   malloc heaps.
>
> Gagandeep Singh (2):
>   app/proc-info: add memory heap dump
>   eal: add total memory size in memory dump APIs

Series applied, thanks.


-- 
David Marchand


      parent reply	other threads:[~2024-10-11 13:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 13:14 [PATCH 1/2] app/proc-info: add memory heap dump Gagandeep Singh
2024-07-02 13:14 ` [PATCH 2/2] eal: add total memory size in memory dump APIs Gagandeep Singh
2024-07-03  8:33 ` [PATCH 1/2] app/proc-info: add memory heap dump Hemant Agrawal
2024-07-29 17:18 ` Thomas Monjalon
2024-07-30 11:10   ` Gagandeep Singh
2024-07-30 11:03 ` [v2 0/2] proc-info memory dump enhancement Gagandeep Singh
2024-07-30 11:03   ` [v2 1/2] app/proc-info: add memory heap dump Gagandeep Singh
2024-10-10  7:16     ` [v3 " Gagandeep Singh
2024-10-10  7:16       ` [v3 2/2] eal: add total memory size in memory dump APIs Gagandeep Singh
2024-10-10 14:52         ` Stephen Hemminger
2024-10-10 14:53         ` Stephen Hemminger
2024-10-10 14:53       ` [v3 1/2] app/proc-info: add memory heap dump Stephen Hemminger
2024-07-30 11:03   ` [v2 2/2] eal: add total memory size in memory dump APIs Gagandeep Singh
2024-10-10  0:25     ` Stephen Hemminger
2024-10-11 13:15   ` David Marchand [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=CAJFAV8w9FavCJx8CF9-EsvqjPyciTzKxsQFH-8Ne3bSzF+p4tw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.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).