ports/openmpi
ports/openmpi
1
1
Форкнуть 0
Код Релизы Активность
f911b1a63d
openmpi/opal/mca/paffinity
История
Shiqing Fan a5281f0434 - 1/4 commit for Windows Visual Studio and CCP support: 
CMakeLists and .windows files.
  In contribs preconfigured and precompiled parts.

This commit was SVN r20108.
2008-12-10 20:59:20 +00:00
..
base Fixed the warnings on the crays. 2008-09-18 11:31:12 +00:00
darwin Fixes from Brian for OS X 10.4. 2008-11-07 22:13:43 +00:00
linux Merge in PLPA v1.2rc2 (README fixes, new version of Autotools, and 2008-09-19 15:05:03 +00:00
posix Revamp the opal mca paffinity interface. We ran into a problem when we encountered machines that had "holes" in their physical processor layout - e.g., machines that supported "hotplugging", or that had unpopulated sockets. To solve that problem, we had to clarify at the API level where we were describing physical vs logical processor info, and then translate accordingly in the underlying implementation. 2008-08-21 19:21:28 +00:00
solaris Revamp the opal mca paffinity interface. We ran into a problem when we encountered machines that had "holes" in their physical processor layout - e.g., machines that supported "hotplugging", or that had unpopulated sockets. To solve that problem, we had to clarify at the API level where we were describing physical vs logical processor info, and then translate accordingly in the underlying implementation. 2008-08-21 19:21:28 +00:00
windows - 1/4 commit for Windows Visual Studio and CCP support: 2008-12-10 20:59:20 +00:00
configure.m4 Modify the configure system in the paffinity framework so that only one component is built. Cleanout variable name conflicts that on some systems prevented building 2008-08-01 22:54:24 +00:00
Makefile.am * fix "make distclean" error in PML 2005-11-20 07:41:09 +00:00
paffinity.h Revamp the opal mca paffinity interface. We ran into a problem when we encountered machines that had "holes" in their physical processor layout - e.g., machines that supported "hotplugging", or that had unpopulated sockets. To solve that problem, we had to clarify at the API level where we were describing physical vs logical processor info, and then translate accordingly in the underlying implementation. 2008-08-21 19:21:28 +00:00