You also have to remove all references to OPAL SOS...
On Jan 12, 2011, at 1:25 PM, Jeff Squyres wrote:
> I back-ported the trunk's paffinity/hwloc component to the v1.5 branch today.
> Here's the things that you need to look out for if you undertake
> back-porting a component from the trunk t
Lots of stuff went in today.
Yay!
Let's see how it shakes out in MTT.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
I back-ported the trunk's paffinity/hwloc component to the v1.5 branch today.
Here's the things that you need to look out for if you undertake back-porting a
component from the trunk to the v1.5 branch...
Remember: the whole autogen.pl infrastructure was not (and will not be) ported
to the v1.
RDMACM or OOB can not effect on performance of this benchmark, since they are
not involved in communication. So I'm not sure that the performance changes
that you see are related to connection manager changes.
About oob - I'm not aware about hangs issue there, the code is very-very old,
we did n
Hi,
For the first problem, I can see that when using rdmacm as openib oob
I get much better performence results (and no hangs!).
mpirun -display-map -np 64 -machinefile voltairenodes -mca btl
sm,self,openib -mca btl_openib_connect_rdmacm_priority 100
imb/src/IMB-MPI1 gather -npmin 64
#bytes
