I took a closer look at this, and I think we&#39;re getting ourselves confused by the rather large differences between what is on the trunk vs the 1.5 branch. The trunk is doing the &quot;am I bound&quot; calculation correctly - it gets the cpubind bitmask and compares it to the allowed/available cpus.<br>
<br>The 1.5 branch has a problem. Jeff and I discussed it a little more, and agreed that I will create a minimal patch to address the issue of direct-launched procs. We definitely don&#39;t want to back-port the logic from the trunk.<br>
<br>Will try to have something next week.<br><br><br><div class="gmail_quote">On Fri, Feb 17, 2012 at 6:03 AM, Jeff Squyres <span dir="ltr">&lt;<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Feb 16, 2012, at 8:16 AM, <a href="mailto:nadia.derbey@bull.net">nadia.derbey@bull.net</a> wrote:<br>

<br>
&gt; Could you please move it to v1.5 (do I need to fill a CMR)?<br>
<br>
</div>Just to clarify - you&#39;re asking for the patch to set WHOLE_SYSTEM when we load the hwloc topology, right?<br>
<br>
If so, please file a CMR.  Note that there&#39;s some differences between how hwloc is used between the trunk and the v1.5 branch; the same commit may not apply exactly from the trunk to v1.5.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Jeff Squyres<br>
<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a><br>
For corporate legal information go to:<br>
<a href="http://www.cisco.com/web/about/doing_business/legal/cri/" target="_blank">http://www.cisco.com/web/about/doing_business/legal/cri/</a><br>
<br>
<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@open-mpi.org">devel@open-mpi.org</a><br>
<a href="http://www.open-mpi.org/mailman/listinfo.cgi/devel" target="_blank">http://www.open-mpi.org/mailman/listinfo.cgi/devel</a><br>
</div></div></blockquote></div><br>