From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Luca Boccassi <lboccass@brocade.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK (and rte_*alloc family) friendly Valgrind
Date: Thu, 11 Feb 2016 08:34:44 +0100 [thread overview]
Message-ID: <1719358.h1p3ccrXDn@xps13> (raw)
In-Reply-To: <1455144896.2805.32.camel@brocade.com>
2016-02-10 22:54, Luca Boccassi:
I created a set of patches for Valgrind that add support for the
> rte_*alloc family of functions. We use it for memcheck (I added support
> for other all the other Valgrind tools like cachegrind as well, but it's
> less tested), and find it extremely useful, since the vanilla version
> cannot intercept and report leaks cause by rte_*alloc functions from
> librte_malloc.
Thank you Luca.
I think it deserves to be visible in the DPDK doc.
What about adding some explanations in
http://dpdk.org/doc/guides/prog_guide/profile_app.html
or
http://dpdk.org/doc/guides/prog_guide/env_abstraction_layer.html#malloc
?
next prev parent reply other threads:[~2016-02-11 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 22:54 Luca Boccassi
2016-02-11 7:34 ` Thomas Monjalon [this message]
2016-02-13 6:47 ` Matthew Hall
2016-02-13 12:15 ` Luca Boccassi
2016-02-13 12:30 ` Luca Boccassi
2016-02-13 19:59 ` Matthew Hall
2016-02-15 9:16 ` Thomas Monjalon
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=1719358.h1p3ccrXDn@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=lboccass@brocade.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).