The uDAPL API can be accessed from the uDAPL BTL, to force its use you
would select it via a MCA parameter.
e.g. add "--mca btl self,sm,udapl" to the mpirun command line
-DON
Andreas Kuntze wrote:
Hello,
is there a way to force Open MPI to use the uDAPL API? I didn't find
anything in
Andreas,
I am going to guess at a minimum the interfaces are up and you can ping
them. On Solaris there is an additional step required and that is
initializing the dat registry. If "/usr/sbin/datadm -v" does not show
some driver output then you would need to run "/usr/sbin/datadm -a
a". I successfully tested INTEL MPI and mvapich2
with uDAPL .
Andreas
Donald Kerr wrote:
Andreas,
I am going to guess at a minimum the interfaces are up and you can
ping them. On Solaris there is an additional step required and that
is initializing the dat registry. If "/usr/sbin/
Looking at that section it appears that we store the port value locally
in udapl_addr and use the local copy, so changing the udapl attribute
may not be doing anything for the BTL. I will run some tests as well.
-DON
Andrew Friedley wrote:
OK, strange but good. Yeah I wouldn't be surprised
Just wondering if/when the slides from Wednesday and Thursday of the
"Open MPI Developer's Workshop" will be posted.
Thanks
-DON
Hey Andrew I have one for you...
I get the following error message on a node that does not have any IB cards
--
[0,1,0]: uDAPL on host burl-ct-v40z-0 was unable to find any NICs.
Another transport will be used instead,
.
If the btl stack is not available no attempt to load and no message is
expected.
So what I am seeing is expected behavior.
Thanks
-DON
Andrew Friedley wrote On 08/10/06 17:44,:
Donald Kerr wrote:
Hey Andrew I have one for you...
I get the following error message on a node that does not have any
