On Jan 31, 2008, at 5:07 PM, Josh Hursey wrote:
For the visualization it would be really nice to see how well tested a
particular interconnect, resource manager, and/or 'feature' is when
ramping up to a release. However these peices of information are hard
to obtain, and in some cases quantify (
On Feb 6, 2008, at 10:25 AM, Jeff Squyres wrote:
On Jan 31, 2008, at 5:07 PM, Josh Hursey wrote:
For the visualization it would be really nice to see how well
tested a
particular interconnect, resource manager, and/or 'feature' is when
ramping up to a release. However these peices of inform
On Wed, Feb/06/2008 10:54:05AM, Josh Hursey wrote:
>
> On Feb 6, 2008, at 10:25 AM, Jeff Squyres wrote:
>
> > On Jan 31, 2008, at 5:07 PM, Josh Hursey wrote:
> >
> >> For the visualization it would be really nice to see how well
> >> tested a
> >> particular interconnect, resource manager, and/
On Feb 6, 2008, at 10:54 AM, Josh Hursey wrote:
So to be clear: does the network field not give you what you need?
The network field gives us exactly what we want. The problem is that
it is not filled in when we run "mpirun foo" since we do not specify
the BTLs on the command line (unless the
On Feb 6, 2008, at 11:32 AM, Ethan Mallove wrote:
For the configure options we *could* parse the config.log to
extract
this data. The question is, if we did this, what do we want to
look?
And is this something we want to do? Is there another way?
I think having a network-like field for
If this is going to be an OMPI-module-specific field, then running
ompi_info is fine. But doesn't the GNU configure MTT module already
have the configure command line?
On Feb 6, 2008, at 1:44 PM, Josh Hursey wrote:
On Feb 6, 2008, at 11:32 AM, Ethan Mallove wrote:
For the configure
On Wed, Feb/06/2008 01:47:16PM, Jeff Squyres wrote:
> If this is going to be an OMPI-module-specific field, then
> running ompi_info is fine. But doesn't the GNU configure
> MTT module already have the configure command line?
The scenario is that I'm using one plug-in to create Solaris
package
Arf; I just realized this is all moot -- ompi_info doesn't have the
argv given to OMPI's configure because we never figured out a way to
do that cleanly. :-\
On Feb 6, 2008, at 4:11 PM, Ethan Mallove wrote:
On Wed, Feb/06/2008 01:47:16PM, Jeff Squyres wrote:
If this is going to be an OMP
