Shoot. Ignore me completely for now. Both are used by the pml in an indirect
way.
-Nathan
From: devel [devel-boun...@open-mpi.org] on behalf of Hjelm, Nathan T
[hje...@lanl.gov]
Sent: Thursday, April 03, 2014 12:25 PM
To: Open MPI Developers
Subject: Re:
Bah. Ignore part of that patch. The btl_rdma_pipeline_send_length is used. The
other one was not. I will provide an updated patch.
-Nathan
From: devel [devel-boun...@open-mpi.org] on behalf of Hjelm, Nathan T
[hje...@lanl.gov]
Sent: Thursday, April 03, 20
What: Remove btl parameters that are no longer used. The parameters are
btl_min_rdma_pipeline_size and btl_min_rdma_pipeline_size
Why: I was working on a short talk talking about the various parameters that
can be used for tuning Open MPI on infiniband systems and I noticed that
several paramet
Maybe?? It would help avoid the unexpected behavior problem, but may ultimately
be too unwieldy for widespread adoption. Still, an option to ponder.
On Apr 3, 2014, at 9:27 AM, Kenneth A. Lloyd wrote:
> Would you consider a user-defined process language library outside of
> OpenMPI? Process fu
Would you consider a user-defined process language library outside of
OpenMPI? Process functors could be defined by compositions in this external
area, and maintenance of the language simply the user's responsibility?
-Original Message-
From: devel [mailto:devel-boun...@open-mpi.org] On Be
I can see the potential utility, but I do have concerns about how to make it
work without causing a lot of user problems:
* as currently implemented, it only affects procs launched via mpirun. This
seems odd - if the user does a direct launch, they would get totally different
behavior? Shouldn'
> mca param file treats any key=val as mca parameter only.
> In order to add parser support for something that is not mca param, will
> require change file syntax and it will look bad, i.e.:
>
> mca btl = sm,self,openib
> env DISPLAY = console:0
>
> I think the current implementation is less in
