d6e415cd41
When looking for PUs inside R_MAXSDL rads, some AIX 6.1 releases return one first rad without any PU. AIX 6.1 00F63F144C00 does (on quad-power7). AIX 6.1 00CBAAC24C00 doesn't (on 16x power6). So we can't assume rad #x contains PU #x. But we already have the right code to fill the cpuset from the rad, so use that to obtain the PU os_index as well. Cannot be used to obtain NUMA node os_index since there's no way to directly retrieve NUMA nodes from rads (mempools seem unrelated). Just keep using #rad for NUMA nodes os_index and document that convention when converting back in set_membind(). Thanks to Hendryk Bockelmann and Erik Schnetter for helping debugging. (cherry picked from commit open-mpi/hwloc@60006c7b88) Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
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).