From: Thomas Monjalon <thomas@monjalon.net>
To: Gagandeep Singh <g.singh@nxp.com>
Cc: dev@dpdk.org, Reshma Pattan <reshma.pattan@intel.com>,
hemant.agrawal@nxp.com
Subject: Re: [PATCH 1/2] app/proc-info: add memory heap dump
Date: Mon, 29 Jul 2024 19:18:08 +0200 [thread overview]
Message-ID: <4318970.mogB4TqSGs@thomas> (raw)
In-Reply-To: <20240702131436.2873832-1-g.singh@nxp.com>
02/07/2024 15:14, Gagandeep Singh:
> --- a/app/proc-info/main.c
> +++ b/app/proc-info/main.c
> @@ -637,6 +638,10 @@ meminfo_display(void)
> rte_memzone_dump(stdout);
> printf("---------- END_MEMORY_ZONES -----------\n");
>
> + printf("------------ HEAP DUMP -------------\n");
Should we add "MALLOC"?
With underscores for consistency?
> + rte_malloc_dump_heaps(stdout);
> + printf("---------- END_HEAP_DUMP -----------\n");
> +
> printf("------------- TAIL_QUEUES -------------\n");
> rte_dump_tailq(stdout);
> printf("---------- END_TAIL_QUEUES ------------\n");
>
next prev parent reply other threads:[~2024-07-29 17:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 13:14 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 [this message]
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 ` [v2 0/2] proc-info memory dump enhancement David Marchand
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=4318970.mogB4TqSGs@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=reshma.pattan@intel.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).