That's fine - please review the standard and let us know.
Meantime, let me explain how the persistent daemon operations currently work
and some of the problems that drove us there (and continue to plague that
mode).
HOW IT CURRENTLY WORKS
First, it is critical to understand the following point: a
I basically agree with Terry, even if your proposal would solve all
the issue I currently face. I think we need to read the MPI2 standard
to make sure we are not on the brink of breaking the standard.
Aurelien
On Jul 27, 2007, at 10:13 , Ralph Castain wrote:
On 7/27/07 7:58 AM, "Terry
On 7/27/07 7:58 AM, "Terry D. Dontje" wrote:
> Ralph Castain wrote:
>
>> WHAT: Proposal to add two new command line options that will allow us to
>>replace the current need to separately launch a persistent daemon to
>>support connect/accept operations
>>
>> WHY:Remove
Ralph Castain wrote:
WHAT: Proposal to add two new command line options that will allow us to
replace the current need to separately launch a persistent daemon to
support connect/accept operations
WHY:Remove problems of confusing multiple allocations, provide a cleaner
WHAT: Proposal to add two new command line options that will allow us to
replace the current need to separately launch a persistent daemon to
support connect/accept operations
WHY:Remove problems of confusing multiple allocations, provide a cleaner
method for connect/
