configury: fix git describe with VPATH
configury: fix a typo in config/opal_config_threads.m4
configury: fix pthread flags for fortran
HCOLL:  Fix OMPI to HCOLL predefined datatypes, Ops mapping
OMPI: btl openib: fix max registarable memory caluclation

    - by default allow to register maximum possible (i.e 2 * total_memory)
      memory. This beheviour can be turned off using mca parameter
      "btl_openib_allow_max_memory_registration"

    - In fallback case, use device specific parameters to calulate
      memory limit.
Merge branch 'master' of https://github.com/open-mpi/ompi
coll/libnbc: fix MPI_Ireduce_scatter for single task communicator
when MPI_IN_PLACE is not used.

that commit fixes a regression introduced
open-mpi/ompi@49e79a9ade6c97e357391923f411e75e38fac346
Added several new COMM_TYPE_<> splits

Using the underlying hardware identification to split
communicators based on locality has been enabled using
the MPI_Comm_Split_Type function.

Currently implemented split's are:
  HWTHREAD
  CORE
  L1CACHE
  L2CACHE
  L3CACHE
  SOCKET
  NUMA
  NODE
  BOARD
  HOST
  CU
  CLUSTER

However only NODE is defined in the standard which is why the
remaning splits are referred to using the OMPI_ prefix instead
of the standard MPI_ prefix.

I have tested this using --without-hwloc and --with-hwloc=<path>
which both give the same output.

NOTE: I think something fishy is going on in the locality operators.
In my test-program I couldn't get the correct split on these requests:
  NUMA, SOCKET, L3CACHE
where I suspected a full communicator but only got one.
Fix commit bffb2b7a4bb49c9188d942201b8a8f04872ff63c which broke pmix server functionality
Merge pull request #326 from zerothi/master

Enabled COMM_TYPE_SPLIT dependent on locality
initial async progress changes for gni
btl/ugni: use MCA_BTL_DES_FLAGS_SIGNAL

Use MCA_BTL_DES_FLAGS_SIGNAL frag flag to indicate
whether or not an interrupt needs to be delivered
along with a control message going through smsg.
btl/ugni: compilation fixes

Fix compilation problems in ugni btl associated with
async progress additions.
btl/ugni: add missing mutex lock
btl/ugni: honor enable_mpi_threads

Honor enable_mpi_threads setting to enable the ugni btl
async progress thread.  If the app doesn't request thread-multiple
the thread will not be created.
btl/ugni: mark btl frags for irqs as btl owned

Make sure frags allocated to generate irqs to wake
the progress thread, etc. set the MCA_BTL_DES_FLAGS_BTL_OWNERSHIP
flag.
btl/ugni: turn off chatty debug in irq cq setup
btl/ugni: switch to using tx cq irqs for rdma

Verified via testing with unit tests, etc. that
in fact BTE TX descriptors using CQs configured to
generate IRQs were in fact working correctly on Cray XC.  Disable
send message back to self and just use IRQs generated
by completion of TX descriptors posted to BTE.
btl/ugni: remove some debug output
btl/ugni: switch to using opal_progress

Switch to invoking opal_progress from the async progress
thread, rather than calling ugni btl specific progress.