openmpi

Jeff Squyres 951c745590 We always have hwloc xml support (now that it's built into to hwloc without needing libxml2). So OPAL_HAVE_HWLOC_XML is no longer necessary. This commit was SVN r25263.		2011-10-11 20:20:59 +00:00
..
base	We always have hwloc xml support (now that it's built into to hwloc	2011-10-11 20:20:59 +00:00
external	Fix some problems with the libevent and hwloc frameworks:	2011-09-21 23:06:13 +00:00
hwloc122ompi	We always have hwloc xml support (now that it's built into to hwloc	2011-10-11 20:20:59 +00:00
configure.m4	We always have hwloc xml support (now that it's built into to hwloc	2011-10-11 20:20:59 +00:00
hwloc.h	Per the RFC from Jeff, move hwloc from opal/mca/common to its own static framework ala libevent. Have ORTE daemons collect the topology info at startup and, if --enable-hwloc-xml is set, send that info back to the HNP for later use. The HNP only retains unique topology "templates" to reduce memory footprint. Have the daemon include the local topology info in the nidmap buffer sent to each app so the apps don't all hammer the local system to discover it for themselves.	2011-09-11 19:02:24 +00:00
Makefile.am	Per the RFC from Jeff, move hwloc from opal/mca/common to its own static framework ala libevent. Have ORTE daemons collect the topology info at startup and, if --enable-hwloc-xml is set, send that info back to the HNP for later use. The HNP only retains unique topology "templates" to reduce memory footprint. Have the daemon include the local topology info in the nidmap buffer sent to each app so the apps don't all hammer the local system to discover it for themselves.	2011-09-11 19:02:24 +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).