From: Linhaifeng <haifeng.lin@huawei.com>
To: Marc Sune <marc.sune@bisdn.de>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] How to check memory leak with dpdk application
Date: Tue, 14 Apr 2015 18:59:27 +0800 [thread overview]
Message-ID: <552CF30F.3080107@huawei.com> (raw)
In-Reply-To: <552C261E.7040608@bisdn.de>
On 2015/4/14 4:25, Marc Sune wrote:
>
>
> On 10/04/15 07:53, Linhaifeng wrote:
>> Hi, all
>>
>> I'am trying to use valgrind to check memory leak with my dpdk application but dpdk always failed to mmap hugepages.
>>
>> Without valgrind it works well.How to run dpdk applications with valgrind?Is there any other way to check memory leak
>> with dpdk applications?
>>
>
> Yes it can be used, just that 3.10 has issues with hugepages. Check this out:
>
> http://article.gmane.org/gmane.comp.networking.dpdk.devel/8058/match=valgrind+hugepages
>
> Marc
>
>
Hi，Marc
Thank you very much!
prev parent reply other threads:[~2015-04-14 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 5:53 Linhaifeng
2015-04-13 20:25 ` Marc Sune
2015-04-14 10:59 ` Linhaifeng [this message]
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=552CF30F.3080107@huawei.com \
--to=haifeng.lin@huawei.com \
--cc=dev@dpdk.org \
--cc=marc.sune@bisdn.de \
/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).