opal MCA params: Move (and adapt) help message to opal help file
check-help-strings.pl: work better when running in a subdir

The script used to get confused if you ran it in a subdir of the OMPI
tree (e.g., it would report help files not found if source code
referred to a help file that was not under the subdir in which it was
run).

Now the script searches the whole tree for help files, but only
analyzes the source from the subdir in which it was started.  Meaning:
it should always find all help files, and won't get confused like it
did before.
contrib: add support for v1.8 branch, add getopt aliases
Fix missing help file.
configury: disable pshmem if buggy compiler is detected

PGI compilers older that 2013 have a buggy preprocessor
that does not support pragma defined in a macro called
itself called from an other macro

cmr=v1.8.2:reviewer=jsquyres
Sigh - I promised to remove these deprecation warnings back in June. My apologies to Dave Goodell and others who requested it.

cmr=v1.8.2:reviewer=dgoodell:subject=remove deprecation warnings for pernode, npernode, and npersocket
If an initial address fails to connect, record that fact and attempt the next address for that proc. If nothing succeeds, then declare failure.

cmr=v1.8.2:reviewer=edgar
Frazzle-frump! Missed that we reset the peer state just before the new check.

Refs #4870
btl/scif: use safe syntax

PGI compilers 2013 and older do not support the following syntax :
mca_btl_scif_modex_t modex = {.port_id = mca_btl_scif_module.port_id};
so split it on two lines

cmr=v1.8.2:reviewer=hjelmn
Track down the last piece of the connection problem. It appears that
providing a netmask of 0 to opal_net_samenetwork results in everything
looking like it is on the same network. Hence, we were not retaining any
of the alternative addresses, so we had no other way to check them.

Refs #4870
revamp of the aggregator selection logic, part 1.
Remove an unnecessary optimization that can cause more trouble than it's worth - just try all the addresses that are given to us.

Refs #4870
Adding a new OPAL hash table routine. Contributed by David Linden of H.P. in partnership
with Mellanox Technologies. This should be added to 


cmr=v1.8.2:subject=New OPAL hash table:reviewer=rhc
Silence warning

Refs #4872
new opal hash table

Decrease the hash table size when an element is removed

cmr=v1.8.2:ticket=#4872
udcm: psn should be 24 bit, new OFED actually checks and fails if it is not 24 bit.
btl/scif: use safe syntax

Thanks to Ashley Pittman for pointing the modex should now be zero'ed

cmr=v1.8.2:ticket=#4871
openib/btl: better detect max reg memory. OFED has no runtime versioning API :(

based on http://www.open-mpi.org/community/lists/users/2014/08/25048.php

reviewed by AlexM
cmr=v1.8.2:reviewer=ompi-rm1.8
Per the PMIx RFC:

WHAT:    Merge the PMIx branch into the devel repo, creating a new
               OPAL “lmix” framework to abstract PMI support for all RTEs.
               Replace the ORTE daemon-level collectives with a new PMIx
               server and update the ORTE grpcomm framework to support
               server-to-server collectives

WHY:      We’ve had problems dealing with variations in PMI implementations,
               and need to extend the existing PMI definitions to meet exascale
               requirements.

WHEN:   Mon, Aug 25

WHERE:  https://github.com/rhc54/ompi-svn-mirror.git

Several community members have been working on a refactoring of the current PMI support within OMPI. Although the APIs are common, Slurm and Cray implement a different range of capabilities, and package them differently. For example, Cray provides an integrated PMI-1/2 library, while Slurm separates the two and requires the user to specify the one to be used at runtime. In addition, several bugs in the Slurm implementations have caused problems requiring extra coding.

All this has led to a slew of #if’s in the PMI code and bugs when the corner-case logic for one implementation accidentally traps the other. Extending this support to other implementations would have increased this complexity to an unacceptable level.

Accordingly, we have:

* created a new OPAL “pmix” framework to abstract the PMI support, with separate components for Cray, Slurm PMI-1, and Slurm PMI-2 implementations.

* Replaced the current ORTE grpcomm daemon-based collective operation with an integrated PMIx server, and updated the grpcomm APIs to provide more flexible, multi-algorithm support for collective operations. At this time, only the xcast and allgather operations are supported.

* Replaced the current global collective id with a signature based on the names of the participating procs. The allows an unlimited number of collectives to be executed by any group of processes, subject to the requirement that only one collective can be active at a time for a unique combination of procs. Note that a proc can be involved in any number of simultaneous collectives - it is the specific combination of procs that is subject to the constraint

* removed the prior OMPI/OPAL modex code

* added new macros for executing modex send/recv to simplify use of the new APIs. The send macros allow the caller to specify whether or not the BTL supports async modex operations - if so, then the non-blocking “fence” operation is used, if the active PMIx component supports it. Otherwise, the default is a full blocking modex exchange as we currently perform.

* retained the current flag that directs us to use a blocking fence operation, but only to retrieve data upon demand
add initial support for non-blocking read and write operations.