From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xueming Li <xuemingl@mellanox.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Asaf Penso <asafp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: add memory dump command
Date: Tue, 7 Apr 2020 10:21:51 +0100 [thread overview]
Message-ID: <d7ac1c0e-c764-a551-9ef6-beb3b18c21fb@intel.com> (raw)
In-Reply-To: <1586054962-5006-2-git-send-email-xuemingl@mellanox.com>
On 4/5/2020 3:49 AM, Xueming Li wrote:
> Introduce new command to dump memory statistics of each socket,
> summary, also show changes since last call.
>
> Usage:
> dump_socket_mem
>
> Signed-off-by: Xueming Li <xuemingl@mellanox.com>
<...>
> @@ -9576,6 +9626,8 @@ static void cmd_dump_parsed(void *parsed_result,
>
> if (!strcmp(res->dump, "dump_physmem"))
> rte_dump_physmem_layout(stdout);
> + else if (!strcmp(res->dump, "dump_socket_mem"))
> + dump_socket_mem(stdout);
> else if (!strcmp(res->dump, "dump_memzone"))
> rte_memzone_dump(stdout);
> else if (!strcmp(res->dump, "dump_malloc")) {
This "dump_malloc" is not in the upstream, which cause a conflict while merging
the patch, which is breaking our automated tests.
It is OK for now, but for later please rebase your patches on latest master.
> @@ -9604,6 +9656,7 @@ static void cmd_dump_parsed(void *parsed_result,
> TOKEN_STRING_INITIALIZER(struct cmd_dump_result, dump,
> "dump_physmem#"
> "dump_memzone#"
> + "dump_socket_mem#"
> "dump_struct_sizes#"
> "dump_ring#"
> "dump_mempool#"
> diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> index 1a9879f..0942ae5 100644
> --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> @@ -539,6 +539,12 @@ Dumps the layout of all memory zones::
>
> testpmd> dump_memzone
>
> +dump socket
> +~~~~~~~~~~~~
Title fixed as "dump socket memory" while merging
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2020-04-07 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 13:03 [dpdk-dev] [PATCH] " Xueming Li
2020-04-02 15:55 ` Ferruh Yigit
2020-04-03 6:53 ` [dpdk-dev] [PATCH v1] " Xueming Li
2020-04-03 6:53 ` Xueming Li
2020-04-03 13:29 ` Ferruh Yigit
2020-04-03 16:04 ` Stephen Hemminger
2020-04-03 16:08 ` Stephen Hemminger
2020-04-03 16:34 ` Morten Brørup
2020-04-05 2:49 ` [dpdk-dev] [PATCH v2] " Xueming Li
2020-04-05 2:49 ` Xueming Li
2020-04-07 9:21 ` Ferruh Yigit [this message]
2020-04-07 11:24 ` Xueming(Steven) Li
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=d7ac1c0e-c764-a551-9ef6-beb3b18c21fb@intel.com \
--to=ferruh.yigit@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=asafp@mellanox.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stephen@networkplumber.org \
--cc=wenzhuo.lu@intel.com \
--cc=xuemingl@mellanox.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).