As was mentioned in prior emails to the devel list and discussed during our 
developer telecons on several occasions, several of us have been working for 
some time to revise the mapping/binding procedure to take advantage of topology 
information.  We were particularly interested in giving users the option of 
mapping to specific resource types (e.g., "map 2 procs on every NUMA node"), 
and binding to various resource levels independent of how the job was mapped.

Small parts of our work has already been committed (e.g., the trunk today will 
return discovered topology info from compute nodes).  We are in final prep to 
bring over the rest of our Mercurial branch 
(https://bitbucket.org/rhc/ompi-hwloc).  We expect to make that commit by the 
end of this week -- this email serves as a "heads up" for the impending change.

Despite best efforts, there will undoubtedly be a settling period for a change 
of this magnitude while we shake out the inevitable bugs as we encounter new 
environments and use-cases.  

We appreciate your patience in advance.

Ralph, Jeff, Josh, and Terry

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/


Reply via email to