We agreed on today's telecon to leave the code in the OMPI code base
for now, but to remove the option from the mpirun man page since
nobody can explain how to use it anyway.
Then we will wait in hope that someone(s) complete the coding of this
"feature" and document its use.
On Oct 13, 2
I agree with Terry and Eugene, but now what are we going to do about it?
This is a potentially very powerful feature.
Ken
> -Original Message-
> From: devel-boun...@open-mpi.org
> [mailto:devel-boun...@open-mpi.org] On Behalf Of Terry Dontje
> Sent: Tuesday, October 13, 2009 7:08 AM
> T
I guess my problem with the manpage or any info on carto in general is
that there is no text that describes what happens if you have a
cartofile and how it affects a job when you pass it in.
--td
Sylvain Jeaugey wrote:
We worked a bit on it and yes, there is some work to do :
* The syntax u
We worked a bit on it and yes, there is some work to do :
* The syntax used to describe the various components is far from being
consistent from one usage to another ("SOCKET", "NODE", ...). We manage to
make things reading the various not up to date example files - but mainly
the code.
* Th
Here is where OMPI uses it:
ompi/mca/btl/openib/btl_openib_component.c:1918:static
opal_carto_graph_t *host_topo;
ompi/mca/btl/openib/btl_openib_component.c:1923:
opal_carto_base_node_t *device_node;
ompi/mca/btl/openib/btl_openib_component.c:1931:device_node =
opal_carto_base_find_n
After rereading the manpage for the umpteenth time I agree with Eugene
that the information provided on cartofile is next to useless. Ok, so
you describe what your node looks like but what does mpirun or libmpi do
with that information? Other than the option to provide the cartofile
it isn't
