Jeff Squyres 338920656f Remove the compile-time proiorities for paffinity modules (they were ... done this way a long time ago for the "gee whiz!" factor -- when in reality, they really only need one-of-many-run-time priority selection). Changed run-time priorities to be as follows: * darwin: 20 * linux: 20 * posix: 10 * solaris: 30 * test: 5 * windows: 20 I have a very dim (possibly untrue) recollection that Solaris needs to have a higher priority than others just to ensure that no other is chosen under Solaris. Make all other "native" components have a priority of 20 (they shouldn't conflict with each other). Make the posix fallback component have a priority of 10. Make the test component priority 5, meaning someone can always select it, but you can also make a "never select me" component that prioritizes itself under test. This commit was SVN r22997.		2010-04-19 22:14:06 +00:00
..
configure.m4	Update Cisco copyrights for consistency	2009-10-07 22:02:32 +00:00
configure.params	Remove the compile-time proiorities for paffinity modules (they were	2010-04-19 22:14:06 +00:00
Makefile.am	Add a new "test" module to the paffinity framework that mimics a system that supports affinity when running on a Mac for development purposes. Only active if specifically called out.	2009-08-26 01:55:30 +00:00
paffinity_test_component.c	Remove the compile-time proiorities for paffinity modules (they were	2010-04-19 22:14:06 +00:00
paffinity_test_module.c	Extend the paffinity test module to allow users to specify the number of sockets and cores - provides an extended ability to mimic archs.	2009-08-29 03:35:39 +00:00
paffinity_test.h	Update Cisco copyrights for consistency	2009-10-07 22:02:32 +00:00