On 12/6/07 8:06 AM, "Shipman, Galen M." wrote:
>>>
>>> Do we really need a complete node map? A far as I can tell, it looks
>>> like the MPI layer only needs a list of local processes. So maybe it
>>> would be better to forget about the node ids at the mpi layer and just
On 12/6/07 8:09 AM, "Shipman, Galen M." wrote:
> Sorry, to be clear that should have been:
>
>> One option is for the RTE to just pass in an enviro variable with a
>> comma-separated list of your local ranks, but that creates a problem down
>> the road when trying to
Sorry, to be clear that should have been:
> One option is for the RTE to just pass in an enviro variable with a
> comma-separated list of your local ranks, but that creates a problem down
> the road when trying to integrate tighter with systems like SLURM where the
> procs would get mass-launched
>>
>> Do we really need a complete node map? A far as I can tell, it looks
>> like the MPI layer only needs a list of local processes. So maybe it
>> would be better to forget about the node ids at the mpi layer and just
>> return the local procs.
>
> I agree, though I don't think we want a
On 12/5/07 8:48 AM, "Tim Prins" wrote:
> Well, I think it is pretty obvious that I am a fan of a attribute system :)
>
> For completeness, I will point out that we also exchange architecture
> and hostname info in the modex.
True - except we should note that hostname
Well, I think it is pretty obvious that I am a fan of a attribute system :)
For completeness, I will point out that we also exchange architecture
and hostname info in the modex.
Do we really need a complete node map? A far as I can tell, it looks
like the MPI layer only needs a list of local
IV. RTE/MPI relative modex responsibilities
The modex operation conducted during MPI_Init currently involves the
exchange of two critical pieces of information:
1. the location (i.e., node) of each process in my job so I can determine
who shares a node with me. This is subsequently used by the