openmpi

Jeff Squyres 9c9d7e77df Commit a fix for hwloc -- still checking with upstream to see if this

will be the final solution.  But I'm committing it now so that
Oracle's Solaris Studio builds can resume.

The issue is that the C++ bindings are now (eventually) including
<hwloc.h>.  We use !__hwloc_inline__ and #define it to an appropriate
value at compile-time.  The issue is that when we're compiling C++
code, we should just set !__hwloc_inline__ to "inline", because that's
a keyword in the C++ language (as opposed to !__inline__, or
somesuch).

This commit was SVN r26418.

2012-05-09 21:03:45 +00:00

base

Per RFC, bring in the following changes:

2012-05-07 14:52:54 +00:00

external

Fixes trac:3043. Looks like some of the improvements to the hwloc132

2012-03-02 20:15:07 +00:00

hwloc132

Commit a fix for hwloc -- still checking with upstream to see if this

2012-05-09 21:03:45 +00:00

configure.m4

Don't force the use of libpci support in hwloc in the default case --

2012-03-22 15:28:35 +00:00

hwloc.h

Per RFC, bring in the following changes:

2012-05-07 14:52:54 +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).