prov/psm: allow rebinding resources to ep

Signed-off-by: Jianxin Xiong <jianxin.xiong@intel.com>
prov/psm: give warning instead of returning error for src_addr check

Signed-off-by: Jianxin Xiong <jianxin.xiong@intel.com>
Merge remote branch 'upstream/master'
man: fill out fi_tsearch flags and errors

List FI_CLAIM as a flag that is applicable to fi_tsearch.
The section was marked with a "write me" before.

-FI_EINVAL and -FI_EOTHER - two other errors that can be
returned.
prov/psm: sync atomics along with RMA ops

Atomic ops are considered a special type of RMA read/write.

Signed-off-by: Jianxin Xiong <jianxin.xiong@intel.com>
Merge pull request #12 from sayantansur/man-tagged

man: fill out fi_tsearch flags
prov/psm: make sure psm_ep_connect is called for each destination

Even if psm_ep_connect hasn't been called, psm_ep_epid_lookup can
still return success because an epaddr could have been created in
response to a remote connection request. It is necessary to have
psmx_ep_connect called for each destnation otherwise hanging could
be observed for later connection requests.

Signed-off-by: Jianxin Xiong <jianxin.xiong@intel.com>
Merge remote branch 'upstream/master'
include: fi_inject_atomic functions

The  fi_inject_atomic call is an optimized version of fi_atomic.  The
fi_inject_atomic function behaves as if the FI_INJECT transfer flag ere
set, and FI_EVENT were not.  That is, the data buffer is available for
reuse immediately on returning from from fi_inject_atomic, and no
completion vent will be generated for this atomic.  The completion event
will be uppressed even  if  the endpoint has not been configured with
FI_EVENT.  See the lags discussion below for more details.

The inject calls are similar to those that are already defined for RMA
and MSGQ.
Merge pull request #51 from j-xiong/master

psm provider bug fixes
Merge pull request #52 from sayantansur/inject-atomic

include: fi_inject_atomic functions