Merge pull request #3033 from shefty/docs

Minor clarifications to man pages

man/fi_mr.3.md

@@ -326,7 +326,12 @@ struct fi_mr_attr (defined below).
 
 Fi_close is used to release all resources associated with a
 registering a memory region.  Once unregistered, further access to the
-registered memory is not guaranteed.
+registered memory is not guaranteed.  Active or queued operations that
+reference a memory region being closed may fail or result in accesses
+to invalid memory.  Applications are responsible for ensuring that a
+MR is no longer needed prior to closing it.  Note that accesses to a
+closed MR from a remote peer will result in an error at the peer.  The
+state of the local endpoint will be unaffected.
 
 When closing the MR, there must be no opened endpoints or counters associated
 with the MR.  If resources are still associated with the MR when attempting to

man/fi_msg.3.md

@@ -248,9 +248,14 @@ fi_sendmsg.
   posted receive operation to generate multiple events as messages are
   placed into the buffer.  The placement of received data into the
   buffer may be subjected to provider specific alignment restrictions.
+
   The buffer will be released by the provider when the available buffer
-  space falls below the specified minimum (see
-  FI_OPT_MIN_MULTI_RECV).
+  space falls below the specified minimum (see FI_OPT_MIN_MULTI_RECV).
+  Note that an entry to the associated receive completion queue will
+  always be generated when the buffer has been consumed, even if other
+  receive completions have been suppressed (i.e. the Rx context has been
+  configured for FI_SELECTIVE_COMPLETION).  See the FI_MULTI_RECV
+  completion flag [`fi_cq`(3)](fi_cq.3.html).
 
 *FI_INJECT_COMPLETE*
 : Applies to fi_sendmsg.  Indicates that a completion should be