From: Xueming Li <xuemingl@mellanox.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Asaf Penso <asafp@mellanox.com>
Subject: [dpdk-dev] [RFC] malloc: add malloc and free log function
Date: Fri, 3 Apr 2020 07:54:14 +0000 [thread overview]
Message-ID: <1585900455-5177-1-git-send-email-xuemingl@mellanox.com> (raw)
DPDK uses second level memory allocation management, this makes
regular memory profiler tool not applicant. This patch trys to
provide a lightweight malloc and free logging, then show leaked
memory entries based on logs.
This tool only target to malloc and free tracking, for memzone
used by ring and mempool, "dump_memzone" in testpmd list them.
There will be another example that enable and dump tracking as
secondary process.
This tool came from Mellanox internal Hackathon, thanks Shahaf Shuler
<shahafs@mellanox.com> who provided the idea.
Xueming Li (1):
malloc: add malloc and free log function
app/test-pmd/cmdline.c | 61 ++++++++++-
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 15 +++
lib/librte_eal/common/eal_memcfg.h | 18 ++++
lib/librte_eal/common/include/rte_malloc.h | 30 +++++-
lib/librte_eal/common/malloc_elem.h | 4 +-
lib/librte_eal/common/rte_malloc.c | 154 +++++++++++++++++++++++++++-
lib/librte_eal/rte_eal_version.map | 2 +
7 files changed, 280 insertions(+), 4 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-04-03 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 7:54 Xueming Li [this message]
2020-04-03 7:54 Xueming Li
2020-04-03 7:54 ` Xueming Li
2020-04-03 9:50 ` Burakov, Anatoly
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=1585900455-5177-1-git-send-email-xuemingl@mellanox.com \
--to=xuemingl@mellanox.com \
--cc=anatoly.burakov@intel.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).