[OMPI devel] Linux memory hooks testing

2013-03-22 Thread Barrett, Brian W
All - In an effort to get 1.7 out the door, I'm asking that everyone who cares tries the memory hooks on Linux to make sure they work as expected on the trunk. That is, if you rely on leave pinned, make sure you get the bandwidth you expect. If you don't, make sure things compile in all your com

Re: [OMPI devel] [EXTERNAL] Re: [OMPI svn] svn:open-mpi r28202 - in trunk: ompi/runtime opal/mca/memory/linux

2013-03-22 Thread Ralph Castain
That got it - thanks!! On Mar 22, 2013, at 9:56 AM, "Barrett, Brian W" wrote: > On 3/22/13 9:53 AM, "Barrett, Brian W" wrote: > >> On 3/22/13 9:35 AM, "Ralph Castain" wrote: >> >>> On Mar 22, 2013, at 8:23 AM, "Barrett, Brian W" >>> wrote: >>> On 3/22/13 9:17 AM, "Ralph Castain" wrot

Re: [OMPI devel] [EXTERNAL] Re: [OMPI svn] svn:open-mpi r28202 - in trunk: ompi/runtime opal/mca/memory/linux

2013-03-22 Thread Barrett, Brian W
On 3/22/13 9:53 AM, "Barrett, Brian W" wrote: >On 3/22/13 9:35 AM, "Ralph Castain" wrote: > >>On Mar 22, 2013, at 8:23 AM, "Barrett, Brian W" >>wrote: >> >>> On 3/22/13 9:17 AM, "Ralph Castain" wrote: >>> I'm afraid this still doesn't work for me - on my Centos box: ../../../o

Re: [OMPI devel] [EXTERNAL] Re: [OMPI svn] svn:open-mpi r28202 - in trunk: ompi/runtime opal/mca/memory/linux

2013-03-22 Thread Barrett, Brian W
On 3/22/13 9:35 AM, "Ralph Castain" wrote: >On Mar 22, 2013, at 8:23 AM, "Barrett, Brian W" >wrote: > >> On 3/22/13 9:17 AM, "Ralph Castain" wrote: >> >>> I'm afraid this still doesn't work for me - on my Centos box: >>> >>> ../../../ompi/.libs/libmpi.so: undefined reference to >>> `opal_memo

Re: [OMPI devel] [EXTERNAL] Re: [OMPI svn] svn:open-mpi r28202 - in trunk: ompi/runtime opal/mca/memory/linux

2013-03-22 Thread Ralph Castain
On Mar 22, 2013, at 8:23 AM, "Barrett, Brian W" wrote: > On 3/22/13 9:17 AM, "Ralph Castain" wrote: > >> I'm afraid this still doesn't work for me - on my Centos box: >> >> ../../../ompi/.libs/libmpi.so: undefined reference to >> `opal_memory_linux_malloc_init_hook' >> >> I tried it with a b

Re: [OMPI devel] [EXTERNAL] Re: [OMPI svn] svn:open-mpi r28202 - in trunk: ompi/runtime opal/mca/memory/linux

2013-03-22 Thread Barrett, Brian W
On 3/22/13 9:17 AM, "Ralph Castain" wrote: >I'm afraid this still doesn't work for me - on my Centos box: > >../../../ompi/.libs/libmpi.so: undefined reference to >`opal_memory_linux_malloc_init_hook' > >I tried it with a brand new checkout of the trunk. Any ideas? Can you run nm on the built li

Re: [OMPI devel] [OMPI svn] svn:open-mpi r28202 - in trunk: ompi/runtime opal/mca/memory/linux

2013-03-22 Thread Ralph Castain
FWIW: I have to revert 28202 and 28164 to get the trunk to build again on Centos 6.2 On Mar 22, 2013, at 8:17 AM, Ralph Castain wrote: > I'm afraid this still doesn't work for me - on my Centos box: > > ../../../ompi/.libs/libmpi.so: undefined reference to > `opal_memory_linux_malloc_init_ho

Re: [OMPI devel] [OMPI svn] svn:open-mpi r28202 - in trunk: ompi/runtime opal/mca/memory/linux

2013-03-22 Thread Ralph Castain
I'm afraid this still doesn't work for me - on my Centos box: ../../../ompi/.libs/libmpi.so: undefined reference to `opal_memory_linux_malloc_init_hook' I tried it with a brand new checkout of the trunk. Any ideas? IIRC, we wound up here because we were trying to avoid rolling libopal into lib

Re: [OMPI devel] Hostfile info argument with MPI_COMM_SPAWN in a Torque environment

2013-03-22 Thread Sebastian Rinke
Thanks for the quick response. >> I'm using OMPI 1.6.4 in a Torque-like environment. >> However, since there are modifications in Torque that prevent OMPI from >> spawning processes the way it does with MPI_COMM_SPAWN, > > That hasn't been true in the past - did you folks locally modify Torque

Re: [OMPI devel] Hostfile info argument with MPI_COMM_SPAWN in a Torque environment

2013-03-22 Thread Ralph Castain
On Mar 21, 2013, at 1:35 PM, Sebastian Rinke wrote: > Dear all, > > I'm using OMPI 1.6.4 in a Torque-like environment. > However, since there are modifications in Torque that prevent OMPI from > spawning processes the way it does with MPI_COMM_SPAWN, That hasn't been true in the past - did y