899bf548a2
The OPAL_PROC_ON_* definitions have been changed from values to flags. This should not cause any problems as these values were already used as flags throughout the code base. Note, there will be a difference between localities produced by the new code and the old. For example, if a machine does not have a level-3 but two cores share a level-1 or level-2 cache cache the level-3 bit will not be set in the locality and OPAL_PROC_ON_LOCAL_L3CACHE will return 0. Before this change it would have returned 1. In addition the OPAL_PROC_ON_LOCAL_* macros have been simplified. Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov> |
||
---|---|---|
.. | ||
base | ||
external | ||
hwloc1110 | ||
configure.m4 | ||
hwloc.h | ||
Makefile.am | ||
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: OPAL_CONFIG_SUBDIR (instead of slurping in hwloc's .m4 files).