1
1
openmpi/opal/mca/paffinity/posix
Jeff Squyres fec7918eea Some paffinity functions had their return status overloaded:
* If < 0, it's an OPAL_ERR_* value
 * If >= 0, it's the actual output value of the function

This is problematic for the OPAL_SOS stuff.  This commit changes those
functions to always return OPAL_* statuses and send the output value
back through output parameters (like 95% of the rest of the code
base).  This avoids the confusion with OPAL_SOS stuff and makes
paffinity work again (e.g., mpirun --bind-to-core ...).

I updated all paffinitiy modules for the new function signatures, and
bumped the paffinity API version up to 2.0.1.  I don't think the
version change will matter, though, because we'll be introducing
support for hardware threads soon, which will either bump the
paffinity version again or we'll replace paffinity with 
a new framework.

This commit was SVN r23197.
2010-05-21 16:55:28 +00:00
..
configure.m4 Gaah; I meant to include a better comment in the last commit but had 2009-04-10 21:16:23 +00:00
configure.params Remove the compile-time proiorities for paffinity modules (they were 2010-04-19 22:14:06 +00:00
Makefile.am Rename the osx paffinity component the "posix" component since it really has nothing osx specific in it - it is just a generic posix call to determine #processors. Set the priority low so that both linux and solaris components override it if they build. It shouldn't build in Windows at all. 2008-07-24 01:54:51 +00:00
paffinity_posix_component.c Some paffinity functions had their return status overloaded: 2010-05-21 16:55:28 +00:00
paffinity_posix_module.c Some paffinity functions had their return status overloaded: 2010-05-21 16:55:28 +00:00
paffinity_posix.h Some paffinity functions had their return status overloaded: 2010-05-21 16:55:28 +00:00