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? ;-)
/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
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}