Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

From: John Robinson (jr_at_[hidden])
Date: 2006-07-11 14:47:29


Hi Edgar,

I really was responding to the original poster, not to you.

The MPI port should be treated as an opaque object, really, right?

I was also wondering whether the user was worried about the TCP port
that MPI daemons use to communicate with each other (assuming there
are daemons involved), but i didn't want to go there. ;-)

thanks,
/jr

---
Edgar Gabriel wrote:
> John Robinson wrote:
> 
>>The MPI publish/lookup calls should handle this, if OpenMPI has them.  I 
>>haven't tried this with OpenMPI yet, but it claims MPI-2 compilance, 
>>right?  ;-)
> 
> 
> of course, but MPI does not say what an MPI port has to be. For Open MPI 
> this is *not* equal to a TCP port number... So you can open a port, 
> publish it, and another process can look this port-name up
> 
> 
>>/jr
>>---
>>Ralph H Castain wrote:
>>
>>>On 7/11/06 11:59 AM, "Edgar Gabriel" <gabriel_at_[hidden]> wrote:
>>>
>>>
>>>
>>>>Abhishek Agarwal wrote:
>>>>
>>>>
>>>>>Hello,
>>>>>
>>>>>Is there a way of providing a specific port number in MPI_Info
>>>>>when using a MPI_Open_port command so that clients know which
>>>>>port number to connect.
>>>>
>>>>the MPI port-name in Open MPI has nothing to do with a TCP port
>>>>number. The port-name right now is a combination of the process
>>>>name ( a tuple of cell id, job id and process id) and a tag used
>>>>for the communication.
>>>>
>>>>Maybe somebody from the RTE group could comment on whether there is
>>>>a possibility to specify a specific port number for OOB
>>>>communication, I am not aware of any right now...
>>>
>>>I'm afraid not - the port number for OOB communications is determined
>>> dynamically be each process, and then communicated between them.
>>>
>>>I'm not sure what your intended purpose is here, of course, but you
>>>don't need to worry about your process being able to "talk" via the
>>>OOB - it's all done automatically during launch.
>>>
>>>Ralph
>>>
>>>
>>>
>>>
>>>>Thanks Edgar
>>>>
>>>>
>>>>
>>>>>Do advice of any solution so that we can create the portname
>>>>>inside the client once we know the port number of server.
>>>>>
>>>>>Thanks Abhishek
>>>>>
>>>>>
>>>>>_______________________________________________ users mailing
>>>>>list users_at_[hidden] 
>>>>>http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>>
>>>>_______________________________________________ users mailing list 
>>>>users_at_[hidden] 
>>>>http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>
>>>
>>>_______________________________________________ users mailing list 
>>>users_at_[hidden] http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>>_______________________________________________
>>users mailing list
>>users_at_[hidden]
>>http://www.open-mpi.org/mailman/listinfo.cgi/users
> 
> 
>