Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Jeff Hammond
No clarification necessary. Standard is not user guide. Semantics are clear from what is defined. Users who don't like the interface can write a library that does what they want. Jeff On Thursday, February 11, 2016, Nathan Hjelm wrote: > > I should also say that I think this is something that m

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Jeff Hammond
Indeed, I ran with MPICH. But I like OpenMPI's choice better here, which is why I said that I would explicitly set the pointer to bull when size is zero. Jeff On Thursday, February 11, 2016, Nathan Hjelm wrote: > > Jeff probably ran with MPICH. Open MPI's are consistent with our choice > of def

[OMPI users] How to map to sockets with 1 per core, but bind to a single hwthread

2016-02-11 Thread Stephen Guzik
Hi, I would like to divide n processes between the sockets on a node, with one process per core, and bind them to a hwthread. Consider a system with 2 sockets, 10 cores per socket, and 2 hwthreads per core. If I enter -np 20 --map-by ppr:1:core --bind-to hwthread then this works as I intend.

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Nathan Hjelm
I should also say that I think this is something that may be worth clarifying in the standard. Either semantic is fine with me but there is no reason to change the behavior if it does not violate the standard. -Nathan On Thu, Feb 11, 2016 at 01:35:28PM -0700, Nathan Hjelm wrote: > > Jeff probab

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Nathan Hjelm
Jeff probably ran with MPICH. Open MPI's are consistent with our choice of definition for size=0: query: me=1, them=0, size=0, disp=1, base=0x0 query: me=1, them=1, size=4, disp=1, base=0x1097e30f8 query: me=1, them=2, size=4, disp=1, base=0x1097e30fc query: me=1, them=3, size=4, disp=1, base=0x1

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Peter Wind
You can be right semantically. But also the sentence "the first address in the memory segment of process i is consecutive with the last address in the memory segment of process i - 1" is not easy to interpret correctly for a zero size segment. There may be good reasons not to allocate the point

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Peter Wind
Thanks Jeff, that was an interesting result. The pointers are here well defined, also for the zero size segment. However I can't reproduce your output. I still get null pointers (output below). (I tried both 1.8.5 and 1.10.2 versions) What could be the difference? Peter mpirun -np 4 a.out

Re: [OMPI users] error openmpi check hdf5

2016-02-11 Thread Rob Latham
On 02/10/2016 12:07 PM, Edgar Gabriel wrote: 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

Re: [OMPI users] MX replacement?

2016-02-11 Thread Rob Latham
On 02/04/2016 11:35 AM, Dave Love wrote: Jeff Hammond writes: On Tuesday, February 2, 2016, Brice Goglin wrote: I announced the end of the Open-MX maintenance to my users in December because OMPI was dropping MX support. Nobody complained. So I don't plan to bring back Open-MX to life nei

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Jeff Hammond
See attached. Output below. Note that the base you get for ranks 0 and 1 is the same, so you need to use the fact that size=0 at rank=0 to know not to dereference that pointer and expect to be writing into rank 0's memory, since you will write into rank 1's. I would probably add "if (size==0) ba

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Jeff Hammond
On Thu, Feb 11, 2016 at 8:46 AM, Nathan Hjelm wrote: > > > On Thu, Feb 11, 2016 at 02:17:40PM +, Peter Wind wrote: > >I would add that the present situation is bound to give problems for some > >users. > >It is natural to divide an array in segments, each process treating its > >

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Nathan Hjelm
On Thu, Feb 11, 2016 at 02:17:40PM +, Peter Wind wrote: >I would add that the present situation is bound to give problems for some >users. >It is natural to divide an array in segments, each process treating its >own segment, but needing to read adjacent segments too. >MPI_

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Peter Wind
I would add that the present situation is bound to give problems for some users. It is natural to divide an array in segments, each process treating its own segment, but needing to read adjacent segments too. MPI_Win_allocate_shared seems to be designed for this. This will work fine as long a

Re: [OMPI users] shared memory zero size segment

2016-02-11 Thread Peter Wind
Yes, that is what I meant. Enclosed is a C example. The point is that the code would logically make sense for task 0, but since it asks for a segment of size=0, it only gets a null pointer, which cannot be used to access the shared parts. Peter - Original Message - > I think Peter