openmpi

Ralph Castain fb9e427320 One last corner case - when encountering an overload condition (e.g., by comm_spawning more procs than we have cores) and we are using the default binding policy, do not bind the new procs to anything as this can cause major problems. Instead, let the spawn succeed since the user didn't specifically ask to be bound, and leave the new procs as unbound. Refs trac:4077 This commit was SVN r30200. The following Trac tickets were found above: Ticket 4077 --> https://svn.open-mpi.org/trac/ompi/ticket/4077		2014-01-09 22:39:34 +00:00
..
base	One last corner case - when encountering an overload condition (e.g., by comm_spawning more procs than we have cores) and we are using the default binding policy, do not bind the new procs to anything as this can cause major problems. Instead, let the spawn succeed since the user didn't specifically ask to be bound, and leave the new procs as unbound.	2014-01-09 22:39:34 +00:00
external	Revamp the handling of wrapper compiler flags. The user flags, main configure	2013-01-29 00:00:43 +00:00
hwloc172	Fix longstanding issue with our multi-project support. Rather than using	2014-01-07 22:11:15 +00:00
configure.m4	Refs trac:4038	2014-01-07 15:58:40 +00:00
hwloc.h	We previously weren't checking all the bits in locality to ensure we had a complete match - instead, we would report "local" to the specified level if only one bit matched. Ensure that a est for locality tests local to the specified level by checking that all bits match.	2013-11-08 04:21:05 +00:00
Makefile.am	Fix longstanding issue with our multi-project support. Rather than using	2014-01-07 22:11:15 +00:00
README.txt	Add some notes about maintaining the hwloc framework.	2011-09-12 19:40:18 +00:00

README.txt

12 Sep 2011

Notes for hwloc component maintainers:

1. There can only be *1* hwloc version component at a time.
   Specifically: if there are multiple hwlocXYZ components (i.e.,
   different versions of hwloc), then they must all be .ompi_ignore'd
   except for 1.  This is because we currently m4_include all of the
   underlying hwloc's .m4 files -- if there are multiple hwlocXYZ
   components, I don't know if m4 will barf at the multiple,
   conflicting AC_DEFUNs, or whether it'll just do something
   completely undefined.

1a. As a consequence, if you're adding a new hwloc version component,
   you'll need to .ompi_ignore all others while you're testing the new
   one. 

2. If someone wants to fix #1 someday, we might be able to do what we
   do for libevent: OMPI_CONFIG_SUBDIR (instead of slurping in hwloc's
   .m4 files).