Re: [Valgrind-users] mpich unable to munmap hugepages

On Thu, 2014-04-03 at 15:33 -0700, janjust wrote: > Philippe, > This worked! Thank you so much for your help. > > So your hypothesis is correct. The huge_pages (at least on my system) have > an alignment issue if MAP_FIXED is used, and no alignment issue if it's not > used. > > The syswrap-generi

Re: [Valgrind-users] mpich unable to munmap hugepages

Philippe, This worked! Thank you so much for your help. So your hypothesis is correct. The huge_pages (at least on my system) have an alignment issue if MAP_FIXED is used, and no alignment issue if it's not used. The syswrap-generic.c seems to always use MAP_FIXED, is that a valgrind requirement?

Re: [Valgrind-users] mpich unable to munmap hugepages

On Thu, 2014-04-03 at 07:21 -0700, janjust wrote: > Philippe, >Thanks a lot for helping with this. > > I ran the code as you suggested. > aprun is a job submission system for our cluster machines. > > Attached is a file with all the output in order: > code, native, strace native, valgrind, st

Re: [Valgrind-users] mpich unable to munmap hugepages

Philippe, Thanks a lot for helping with this. I ran the code as you suggested. aprun is a job submission system for our cluster machines. Attached is a file with all the output in order: code, native, strace native, valgrind, strace -f valgrind If you look at the strace -f valgrind output, at

Re: [Valgrind-users] mpich unable to munmap hugepages

On Wed, 2014-04-02 at 07:17 -0700, janjust wrote: > ah ok so this is a virtual filesystem or something, I'm still unsure what is > going on. > the example you provided succeeds for me as well, but...this file: > > > /var/lib/hugetlbfs/global/pagesize-2097152/hugepagefile.MPICH.0.26201.kvs_4761352

Re: [Valgrind-users] mpich unable to munmap hugepages

ah ok so this is a virtual filesystem or something, I'm still unsure what is going on. the example you provided succeeds for me as well, but...this file: > /var/lib/hugetlbfs/global/pagesize-2097152/hugepagefile.MPICH.0.26201.kvs_4761352 Doesn't exist or something else is going on… $ls /var/lib d

Re: [Valgrind-users] mpich unable to munmap hugepages

On Mon, 2014-03-31 at 14:43 -0700, janjust wrote: > (hm my direct reply seems to be getting rejected) > > Yes, > The output is rather large so I attached 3 files that were the result of > running it with 2 procs. 1 for stdout and the other two are from > --log-file=valgrind.%p > -Tommy > > val.ou

Re: [Valgrind-users] mpich unable to munmap hugepages

(hm my direct reply seems to be getting rejected) Yes, The output is rather large so I attached 3 files that were the result of running it with 2 procs. 1 for stdout and the other two are from --log-file=valgrind.%p -Tommy val.out valgr

Re: [Valgrind-users] mpich unable to munmap hugepages

> Le 31 mars 2014 à 22:01, janjust a écrit : > > > Thanks for replying! > The entire program output is at the bottom. > > The error is: > Unable to mmap hugepage 4194304 bytes > Unable to mmap hugepage 4194304 bytes Can you run with --trace-syscalls=yes -v -v -v -d -d- d to have more info about w

Re: [Valgrind-users] mpich unable to munmap hugepages

Thanks for replying! The entire program output is at the bottom. The error is: Unable to mmap hugepage 4194304 bytes Unable to mmap hugepage 4194304 bytes This is surely mpich specific , as ompi works just fine. The application is very simple, just a simple hello-world example with MPI_Init, send

Re: [Valgrind-users] mpich unable to munmap hugepages

On Mon, 2014-03-31 at 07:23 -0700, janjust wrote: > Hi, Hello, >I'm trying to run a cray-mpich mpi application under valgrind; however, > I'm getting an error message from mpich that it cannot unmap/remap huge > pages. What error msg do you get ? > Did anyone encounter this problem before? An

[Valgrind-users] mpich unable to munmap hugepages

Hi, I'm trying to run a cray-mpich mpi application under valgrind; however, I'm getting an error message from mpich that it cannot unmap/remap huge pages. Did anyone encounter this problem before? Any workarounds? Thanks! -- View this message in context: http://valgrind.10908.n7.nabble.com/