From: Stephen Hemminger <stephen@networkplumber.org>
To: Xueming Li <xuemingl@mellanox.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, Asaf Penso <asafp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v1 1/2] malloc: support malloc and free tracking log
Date: Tue, 7 Apr 2020 22:11:46 -0700 [thread overview]
Message-ID: <20200407221146.386a8006@hermes.lan> (raw)
In-Reply-To: <1586318694-31358-2-git-send-email-xuemingl@mellanox.com>
On Wed, 8 Apr 2020 04:04:53 +0000
Xueming Li <xuemingl@mellanox.com> wrote:
> * Dump contents of all malloc heaps to a file.
> diff --git a/lib/librte_eal/rte_eal_version.map b/lib/librte_eal/rte_eal_version.map
> index f9ede5b..25c4b13 100644
> --- a/lib/librte_eal/rte_eal_version.map
> +++ b/lib/librte_eal/rte_eal_version.map
> @@ -338,4 +338,7 @@ EXPERIMENTAL {
>
> # added in 20.05
> rte_log_can_log;
> + rte_malloc_log_init;
> + rte_malloc_log_dump;
> + rte_malloc_log_stop;
> };
Looks like other entries were indented with tabs and you used spaces?
next prev parent reply other threads:[~2020-04-08 5:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 7:54 [dpdk-dev] [RFC] malloc: add malloc and free log function Xueming Li
2020-04-03 7:54 ` Xueming Li
2020-04-03 9:50 ` Burakov, Anatoly
2020-04-08 4:04 ` [dpdk-dev] [PATCH v1 0/2] malloc: support malloc and free tracking log Xueming Li
2020-04-17 8:03 ` [dpdk-dev] [RFC v2 " Xueming Li
2020-04-17 8:03 ` [dpdk-dev] [RFC v2 1/2] " Xueming Li
2020-04-17 8:03 ` [dpdk-dev] [RFC v2 2/2] app/testpmd: " Xueming Li
2020-04-21 13:41 ` Iremonger, Bernard
2020-07-30 15:10 ` Somnath Kotur
2020-07-30 15:13 ` Xueming(Steven) Li
2020-07-30 15:30 ` Somnath Kotur
2020-04-08 4:04 ` [dpdk-dev] [PATCH v1 1/2] malloc: " Xueming Li
2020-04-08 5:10 ` Stephen Hemminger
2020-04-08 5:11 ` Stephen Hemminger [this message]
2020-04-08 6:45 ` Xueming(Steven) Li
2020-04-08 4:04 ` [dpdk-dev] [PATCH v1 2/2] app/testpmd: " Xueming Li
2020-04-16 10:10 ` Iremonger, Bernard
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=20200407221146.386a8006@hermes.lan \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).