Re: [OMPI users] shared memory zero size segment

I think Peter's point is that if - the windows uses contiguous memory *and* - all tasks knows how much memory was allocated by all other tasks in the window then it could/should be possible to get rid of MPI_Win_shared_query that is likely true if no task allocates zero byte. now, if a task

Re: [OMPI users] shared memory zero size segment

On Wed, Feb 10, 2016 at 8:44 AM, Peter Wind wrote: > I agree that in practice the best practice would be to use > Win_shared_query. > > Still I am confused by this part in the documentation: > "The allocated memory is contiguous across process ranks unless the info > key

Re: [hwloc-users] [WARNING: A/V UNSCANNABLE] object intersection without inclusion

Hello compute-0-12 reports totally buggy NUMA information: $ cat compute-0-12/sys/devices/system/node/node*/cpumap ,00ff ,ff00ff00 ,00ff , $ cat compute-0-0/sys/devices/system/node/node*/cpumap ,00ff ,ff00 ,00ff

Re: [OMPI users] a single build of Open MPI that can be used with multiple GCC versions

David, I you use modules to mange your PATH and LD_LIBRARY_PATH and load only the gcc tht you want when you build openmpi and your applications that sould fix it going forward. Doug > On Feb 10, 2016, at 10:58 AM, David Shrader wrote: > > Hello, > > Is it possible to use

[hwloc-users] object intersection without inclusion

Hello there I'm facing an issue with hwloc 1.5.3 (old, i know, but it's the stock centos 6 package) in that a single node emits this message whenever i run any MPI-enabled program. * Hwloc has encountered what looks

Re: [OMPI users] error openmpi check hdf5

yes and no :-) That particular functions was fixed, but there are a few other especially in the shardefp framework that would cause similar problems if compiled without RTLD_GLOBAL. But more importantly, I can confirm that ompio in the 1.8 and 1.10 series does *not* pass the HDF5 tests and

[OMPI users] a single build of Open MPI that can be used with multiple GCC versions

Hello, Is it possible to use a single build of Open MPI against multiple versions of GCC if the versions of GCC are from the same release series? I was under the assumption that as long as a binary-compatible compiler was used, it was possible to "swap out" the compiler from underneath Open

Re: [OMPI users] shared memory zero size segment

I agree that in practice the best practice would be to use Win_shared_query. Still I am confused by this part in the documentation: "The allocated memory is contiguous across process ranks unless the info key alloc_shared_noncontig is specified. Contiguous across process ranks means that the

Re: [OMPI users] shared memory zero size segment

I don't know about bulletproof, but Win_shared_query is the *only* valid way to get the addresses of memory in other processes associated with a window. The default for Win_allocate_shared is contiguous memory, but it can and likely will be mapped differently into each process, in which case only

[OMPI users] error openmpi check hdf5

Edgar, It seems this the consequence of an abstraction violation (fcoll/two_phases directly calls the io/ompio component) and that was fixed in master. Can you confirm that ? Delphine, The problem should disappear if you use romio instead of ompio Cheers, Gilles On Wednesday, February 10,

Re: [OMPI users] error openmpi check hdf5

Delphine, I am surprised you are using ompio with openmpi 1.8 series. The default is to use romio Did you explicitly ask for ompio ? If not, can you check your environment and ensure you are not mixing openmpi 1.8 and v2.x ? Cheers, Gilles On Wednesday, February 10, 2016, Delphine Ramalingom <

Re: [OMPI users] shared memory zero size segment

Peter, The bulletproof way is to use MPI_Win_shared_query after MPI_Win_allocate_shared. I do not know if current behavior is a bug or a feature... Cheers, Gilles On Wednesday, February 10, 2016, Peter Wind wrote: > Hi, > > Under fortran, MPI_Win_allocate_shared is called

Re: [OMPI users] error openmpi check hdf5

It's version 1.8.1. Regards Delphine *Delphine Ramalingom Barbary | Ingénieure en Calcul Scientifique * Direction des Usages du Numérique (DUN) Centre de Développement du Calcul Scientifique TEL : 02 62 93 84 87- FAX : 02 62 93 81 06 Le 10/02/2016 15:50, Edgar

Re: [OMPI users] error openmpi check hdf5

I have tested 1.8.5 and 1.10.2, both fail. (And Intel and Gnu compilers). Peter - Original Message - > which version of Open MPI is this? > Thanks > Edgar > On 2/10/2016 4:13 AM, Delphine Ramalingom wrote: > > Hello, > > > I try to compile a parallel version of hdf5. > > > I have

Re: [OMPI users] error openmpi check hdf5

which version of Open MPI is this? Thanks Edgar On 2/10/2016 4:13 AM, Delphine Ramalingom wrote: Hello, I try to compile a parallel version of hdf5. I have error messages when I check with openmpi. Support on HDF5 told me that the errors seem related to the new ompio implementation inside

Re: [OMPI users] shared memory zero size segment

Sorry for that, here is the attachement! Peter - Original Message - > Peter -- > > Somewhere along the way, your attachment got lost. Could you re-send? > > Thanks. > > > > On Feb 10, 2016, at 5:56 AM, Peter Wind wrote: > > > > Hi, > > > > Under fortran,

Re: [OMPI users] shared memory zero size segment

- Original Message - > Peter -- > > Somewhere along the way, your attachment got lost. Could you re-send? > > Thanks. > > > > On Feb 10, 2016, at 5:56 AM, Peter Wind wrote: > > > > Hi, > > > > Under fortran, MPI_Win_allocate_shared is called with a window size

Re: [OMPI users] shared memory zero size segment

Peter -- Somewhere along the way, your attachment got lost. Could you re-send? Thanks. > On Feb 10, 2016, at 5:56 AM, Peter Wind wrote: > > Hi, > > Under fortran, MPI_Win_allocate_shared is called with a window size of zero > for some processes. > The output pointer is

[OMPI users] shared memory zero size segment

Hi, Under fortran, MPI_Win_allocate_shared is called with a window size of zero for some processes. The output pointer is then not valid for these processes (null pointer). Did I understood this wrongly? shouldn't the pointers be contiguous, so that for a zero sized window, the pointer should

[OMPI users] error openmpi check hdf5

Hello, I try to compile a parallel version of hdf5. I have error messages when I check with openmpi. Support on HDF5 told me that the errors seem related to the new ompio implementation inside open MPI for MPI-I/O. He suggests that I talk to the OMPI mailing list to resolve these errors.

Re: [OMPI users] OMPI users] Fortran vs C reductions

Gilles Gouaillardet writes: >> implementation. Must I compile in support for being called with >> MPI_DOUBLE_COMPLEX? >> > does that really matter ? Possibly. For example, if the library needed to define some static data, its setup might involve communicating values before