Nathan Hjelm 13643f5b6e btl/vader: improved single-copy support ... This commit makes the folowing changes: - Add support for the knem single-copy mechanism. Initially vader will only support the synchronous copy mode. Asynchronous copy support may be added int the future. - Improve Linux cross memory attach (CMA) when using restrictive ptrace settings. This will allow Open MPI to use CMA without modifying the system settings to support ptrace attach (see /etc/sysctl.d/10-ptrace.conf). - Allow runtime selection of the single copy mechanism. The default behavior is to use the best available. The priority list of single-copy mehanisms is as follows: xpmem, cma, and knem. - Allow disabling support for kernel-assisted single copy. - Some tuning and bug fixes.		2014-10-20 11:44:52 -06:00
..
asm	We haven't supported SPARC 8 in a long time, so remove the atomics reference. Thanks to Paul Hargrove for bringing it to our attention.	2014-08-05 14:49:34 +00:00
class	Mark all instances where atomic operations are used but their return value is unnecessary	2014-10-15 21:47:32 -04:00
datatype	Remove unnecessary includes from the datatype	2014-10-15 21:49:32 -04:00
dss	Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.	2014-10-10 11:39:08 -07:00
etc	Backing out the Open SHMEM project	2013-02-12 17:45:27 +00:00
include	Per the PMIx RFC:	2014-08-21 18:56:47 +00:00
mca	btl/vader: improved single-copy support	2014-10-20 11:44:52 -06:00
memoryhooks	Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.	2014-10-10 11:39:08 -07:00
runtime	Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.	2014-10-10 11:39:08 -07:00
threads	Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.	2014-10-10 11:39:08 -07:00
tools	Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.	2014-10-10 11:39:08 -07:00
util	Revert "Fix heterogeneous support"	2014-10-16 12:24:38 +09:00
win32	windows: effectively revert r32449	2014-08-08 11:36:45 +00:00
Makefile.am	Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.	2014-10-10 11:39:08 -07:00
win_makefile	George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)	2014-07-26 00:47:28 +00:00