That's pretty weird, but you're right. Here is the code that do
exactly what you state.
} else if(strcmp(ompi_mtl_base_selected_component-
>mtl_version.mca_component_name, "psm") != 0) {
/* if mtl is not PSM then back down priority, and require the
user to */
/* specify
George -
I don't care what we end up doing, but what you state is wrong. We do
not use the CM for all other MTLs by default. PSM is the *ONLY* MTL
that will cause CM to be used by default. Portals still falls back to
OB1 by default. Again, don't care, don't want to change, just want
t
This topic was raised on the mailing list quite a few times. There is
a major difference between the PSM and the MX support. For PSM there
is just an MTL, which makes everything a lot simpler. The problem with
MX is that we have an MTL and a BTL. In order to figure out which one
to use, we
Thanks Brian -- I updated the README here and will CMR it over to v1.3:
https://svn.open-mpi.org/trac/ompi/changeset/20265
On Jan 13, 2009, at 8:18 PM, Brian Barrett wrote:
On Jan 13, 2009, at 5:48 PM, Patrick Geoffray wrote:
Jeff Squyres wrote:
Gaah! I specifically asked Patrick and G
On Jan 13, 2009, at 5:48 PM, Patrick Geoffray wrote:
Jeff Squyres wrote:
Gaah! I specifically asked Patrick and George about this and they
said that the README text was fine. Grr...
When I looked at that time, I vaguely remember that _both_ PMLs were
initialized but CM was eventually use
Jeff Squyres wrote:
Gaah! I specifically asked Patrick and George about this and they said
that the README text was fine. Grr...
When I looked at that time, I vaguely remember that _both_ PMLs were
initialized but CM was eventually used because it was the last one. It
looked broken, but it
Gaah! I specifically asked Patrick and George about this and they
said that the README text was fine. Grr...
I'll update.
On Jan 13, 2009, at 3:38 PM, Bogdan Costescu wrote:
On Tue, 13 Jan 2009, Brian W. Barrett wrote:
The bottom line, however, is that the OB1 PML will be the default
*U
On Tue, 13 Jan 2009, Brian W. Barrett wrote:
The bottom line, however, is that the OB1 PML will be the default
*UNLESS* the PSM (PathScale/Qlogic) MTL can be chosen, in which case
the CM PML is used by default.
OK, then the README file is wrong or I don't read it properly... In
the section "
The selection logic for the PML is very confusing and doesn't follow the
standard priority selection. The reasons for this are convoluted and not
worth discussing here. The bottom line, however, is that the OB1 PML will
be the default *UNLESS* the PSM (PathScale/Qlogic) MTL can be chosen, in
On Tue, 13 Jan 2009, Tim Mattox wrote:
The cm PML does not use BTLs..., only MTLs, so
... the BTL selection is ignored.
OK, thanks for clarifying this bit, but...
The README for 1.3b2 specifies that CM is now chosen if possible; in my
trials, when I specify CM+BTL, it doesn't complain and wo
Hi Bogdan,
Sorry for such a late reply to your e-mail. Glad to hear that the
performance anomaly you mentioned below is now gone with 1.3rc3.
But I noticed that we either didn't explain something well enough, or not
at all... The cm PML does not use BTLs..., only MTLs, so your
suggested commandl
Hi!
In testing the 1.3b2, I have encountered a rather strange behaviour.
First the setup:
dual-CPU dual-core x86_64 with Myrinet 10G card
self compiled Linux kernel 2.6.22.18, MX 1.2.7(*)
GCC-4.1.2 (from Debian etch), Torque 2.1.10
OpenMPI 1.3b2 (tar.gz from downl
12 matches
Mail list logo
