On Oct 3, 2007, at 12:43 PM, Torje Henriksen wrote:
I was wondering if you could point me to any information regarding
these
components. I got the source code of course, but other than that.
I believe that there are no docs on how the sm btl works, but the
people who wrote it are on this l
One of the assumptions about the MTL¹s is that only a given MTL can handle
the message
matching for communications. This is done to accommodate mpi-like network
stack that
also handle the MPI message matching, which often do not expose their
internal data
structures used for matching. Open MPI
On Oct 8, 2007, at 10:00 PM, Andreas Knüpfer wrote:
- yes, we might move vanmpirtrace to ./ompi/contrib/vampirtrace/,
why not. but since we agreed on the current location ./tracing/
vampirtrace/ we should not rush it just because another software is
coming to openmpi, should we?
I actually
Jeff Squyres wrote:
Is this in the production VT, or is this OMPI-specific functionality?
If it's OMPI-specific functionality, I would vote to not have it.
One of my big problems with this idea is that we lose the concept of
shipping a single unit of Open MPI. If someone sends us a bug re
On Oct 9, 2007, at 4:07 PM, Edgar Gabriel wrote:
One of my big problems with this idea is that we lose the concept of
shipping a single unit of Open MPI. If someone sends us a bug report
concerning VT, we no longer have a solid idea of what version they
are running because they may have replace
That was long ago, on the first draft of the ORTE. Completely useless
by now, so go ahead and remove it.
george.
On Oct 8, 2007, at 10:01 AM, Tim Prins wrote:
WHAT: Remove the opal message buffer code
WHY: It is not used
WHERE: Remove references from opal/mca/base/Makefile.am and
On Oct 4, 2007, at 3:06 PM, Jinhui Qin wrote:
sib:sharcnet$ mpirun -n 3 ~/openMPI_stuff/Hello
Process 0.1.1 is unable to reach 0.1.2 for MPI communication.
If you specified the use of a BTL component, you may have
forgotten a component (such as "self") in the list of
usable components.
This i
