DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marc Sune <marc.sune@bisdn.de>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Valgrind and DPDK - does it work ?
Date: Fri, 07 Nov 2014 04:35:39 +0100	[thread overview]
Message-ID: <545C3E0B.6060809@bisdn.de> (raw)
In-Reply-To: <20141107010447.GA19666@mhcomputing.net>

On 07/11/14 02:04, Matthew Hall wrote:
> On Fri, Nov 07, 2014 at 01:22:49AM +0100, Marc Sune wrote:
>> Found some time to have a close look. I also wanted to check a DPDK app
>> against valgrind. It works!
>>
>> I downloaded and compiled valgrind from sources (3.10.0) and applied
>> (manually) this patch:
>>
>> https://bugs.kde.org/attachment.cgi?id=85950&action=edit
>>
>> (Applied around line 2216)
>>
>>  From this post:
>>
>> http://valgrind.10908.n7.nabble.com/mpich-unable-to-munmap-hugepages-td49150.html
>>
>> Happy debugging
>> Marc
> Marc,
>
> This is just AMAZING!!! I have wished for it for many years for DPDK, ever
> since I used it in beta before it went GA.
Thanks

Most kudos though (if not all), should go to T. Janjusic. I just found 
it and backported to the latest stable:

https://bugs.kde.org/show_bug.cgi?id=333051

>
> Would it be possible to post your modification of Valgrind in Github,
> Bitbucket, or some other repo? I'd like to try this out on my app, too.

Sure, it is a good idea.

I just did a quick&dirty import of the latest stable release 3.10.0. No 
git-svn , or anything fancy (github import failed, silently ignoring 
files...)  no gitignore too. And then I applied the patch:

https://github.com/bisdn/valgrind-hugepages

Please note the comment in README.md, I cannot provide any support or 
take any responsibility. We will also delete this repo once there is a 
stable release.

But you can at least try it, should work ;)

>
> Also, not sure if anybody sent this upstream to Valgrind, but if not, we
> really should, so it just works by default from now on.
It already is, there is simply no stable release yet (see Phillipe comment):

https://bugs.kde.org/show_bug.cgi?id=333051#c8

Cheers
Marc
>
> Thanks,
> Matthew.

      reply	other threads:[~2014-11-07  3:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 11:42 Morten Jagd Christensen
2014-11-07  0:22 ` Marc Sune
2014-11-07  0:29   ` Marc Sune
2014-11-07  1:04   ` Matthew Hall
2014-11-07  3:35     ` Marc Sune [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=545C3E0B.6060809@bisdn.de \
    --to=marc.sune@bisdn.de \
    --cc=dev@dpdk.org \
    --cc=mhall@mhcomputing.net \
    /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).