Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: [OMPI users] mixed myrinet/non-myrinet nodes
From: M Jones (jonesm_at_[hidden])
Date: 2008-01-15 09:49:40


   We have a mixed environment in which roughly 2/3 of the nodes
in our cluster have myrinet (mx 1.2.1), while the full cluster has
gigE. Running open-mpi exclusively on myrinet nodes or exclusively
on non-myrinet nodes is fine, but mixing the two nodes types
results in a runtime error (PML add procs failed), no matter what --mca
flags I try to use to push the traffic onto tcp (note that
--mca mtl ^mx --mca btl ^mx does appear to use tcp, as long as all
of the nodes have myrinet cards, but not in the mixed case).

I thought that we would be able to use a single open-mpi build to
support both networks (and users would be able to request mx nodes if
they need them using the batch queuing system, which they are
already accustomed to). Am I missing something (or just doing
something dumb)? Compiling mpi implementations for each compiler suite
is bad enough, add in separate builds for networks and it just gets
worse ...