I believe that the only problem with that procedure is that it automatically
connects the new application with *all* pre-existing applications. There is
no discrimination possible as your client doesn't know the server's jobid,
nor is there any way for it to "discover" that information.
So this
Ralph Castain wrote:
On 7/17/07 5:37 AM, "Jeff Squyres" wrote:
On Jul 16, 2007, at 2:28 PM, Matthew Moskewicz wrote:
MPI-2 does support the MPI_COMM_JOIN and MPI_COMM_ACCEPT/
MPI_COMM_CONNECT models. We do support this in Open MPI, but the
restrictions (in
On 7/17/07 5:37 AM, "Jeff Squyres" wrote:
> On Jul 16, 2007, at 2:28 PM, Matthew Moskewicz wrote:
>
>>> MPI-2 does support the MPI_COMM_JOIN and MPI_COMM_ACCEPT/
>>> MPI_COMM_CONNECT models. We do support this in Open MPI, but the
>>> restrictions (in terms of ORTE) may
On Jul 16, 2007, at 2:28 PM, Matthew Moskewicz wrote:
MPI-2 does support the MPI_COMM_JOIN and MPI_COMM_ACCEPT/
MPI_COMM_CONNECT models. We do support this in Open MPI, but the
restrictions (in terms of ORTE) may not be sufficient for you.
perhaps i'll experiment -- any clues as to what the
hi again,
>>> i'll probably just continue experimenting on my own for the
>>> moment (tracking
>>> any updates to the main trunk LSF support) to see if i can figure
>>> it out. any
>>> advice the best way to get such back support into trunk, if and
>>> when if exists
>>> / is working?
>>
>> The