Hi,
I'm working with MPI_Comm_spawn and I have some error messages.
The code is relatively simple:
#include
#include
#include
#include
#include
int main(int argc, char ** argv){
int i;
int rank, size, child_rank;
char nomehost[20];
MPI_Comm parent, intercom
On Mon, Dec 5, 2011 at 16:12, Ralph Castain wrote:
> Sounds like we should be setting this value when starting the process - yes?
> If so, what is the "good" value, and how do we compute it?
I've also been just looking at this for the past few days. What I came
up with is a small script psm_shctx
We've never recommended the use of dapl on Linux. I think it might have worked
at one time, but I don't think anyone bothered to maintain it.
On Linux, you should probably use native verbs support, instead.
On Dec 2, 2011, at 1:21 PM, Paul Kapinos wrote:
> Dear Open MPI developer,
>
> OFED
-
Arnaud HERITIER
Meteo France International
+33 561432940
arnaud.herit...@mfi.fr
--
On Mon, Dec 5, 2011 at 6:12 PM, Ralph Castain wrote:
>
> On Dec 5, 2011, at 5:49 AM, arnaud Heritier wrote
On Dec 5, 2011, at 5:49 AM, arnaud Heritier wrote:
> Hello,
>
> I found the solution, thanks to Qlogic support.
>
> The "can't open /dev/ipath, network down (err=26)" message from the ipath
> driver is really misleading.
>
> Actually, this is an hardware context problem on the Qlogic PSM. PSM
Hello,
I found the solution, thanks to Qlogic support.
The "can't open /dev/ipath, network down (err=26)" message from the ipath
driver is really misleading.
Actually, this is an hardware context problem on the Qlogic PSM. PSM can't
allocate any hardware context for the job because other(s) MPI
