Nathan and Kawashima-san,
i just committed
https://github.com/open-mpi/ompi/commit/6eac6a8b002d3992182c141334a7009ba5fa6176
the datafile is still named with the CID, but it is now created
in ompi_process_info.proc_session_dir
instead of
ompi_process_info.job_session_dir
the file is created on
Gilles,
I see. Thanks!
Takahiro Kawashima,
MPI development team,
Fujitsu
> Kawashima-san,
>
> we always duplicate the communicator, and use the CID of the duplicated
> communicator, so bottom line,
> there cannot be more than one window per communicator.
>
> i will double check about using PI
Kawashima-san,
we always duplicate the communicator, and use the CID of the duplicated
communicator, so bottom line,
there cannot be more than one window per communicator.
i will double check about using PID. if a broadcast is needed, i would
rather use the process name of rank 0 in order to
Nathan,
Is is sufficient?
Multiple windows can be created on a communicator.
So I think PID + CID is not sufficient.
Possible fixes:
- The root process creates a filename with a random number
and broadcast it in the communicator.
- Use per-communicator counter and use it in the filename.
Regar
IU has switched the www.open-mpi.org web site to be 100% https (i.e., if you go
to an http://www.open-mpi.org/BLAH URL, you'll be automatically redirected to
https://www.open-mpi.org/BLAH).
SSL for all!
Please let us know if you run into any problems with the web site.
--
Jeff Squyres
jsquy..
Hmm, I think you are correct. There may be instances where two different
local processes may use the same CID for different communicators. It
should be sufficient to add the PID of the current process to the
filename to ensure it is unique.
-Nathan
On Tue, Feb 02, 2016 at 09:33:29PM +0900, Gille
Nathan,
the sm osc component uses communicator CID to name the file that will be
used to create shared memory segments.
if I understand and correctly, two different communicators coming from the
same MPI_Comm_split might share the same CID, so CID (alone) cannot be used
to generate a unique per co
Lisandro,
here is attached a patch (master does things differently, so this has to
be a one-off patch anyway)
could you please give it a try ?
btw, how do you get these warnings automatically ?
Cheers,
Gilles
On 2/2/2016 12:02 AM, Lisandro Dalcin wrote:
You might argue that the attached te
