3401bd2b07
This is required to tighten up the BTL semantics. Ordering is not guaranteed, but, if the BTL returns a order tag in a descriptor (other than MCA_BTL_NO_ORDER) then we may request another descriptor that will obey ordering w.r.t. to the other descriptor. This will allow sane behavior for RDMA networks, where local completion of an RDMA operation on the active side does not imply remote completion on the passive side. If we send a FIN message after local completion and the FIN is not ordered w.r.t. the RDMA operation then badness may occur as the passive side may now try to deregister the memory and the RDMA operation may still be pending on the passive side. Note that this has no impact on networks that don't suffer from this limitation as the ORDER tag can simply always be specified as MCA_BTL_NO_ORDER. This commit was SVN r14768. |
||
|---|---|---|
| .. | ||
| .ompi_ignore | ||
| .ompi_unignore | ||
| btl_template_component.c | ||
| btl_template_endpoint.c | ||
| btl_template_endpoint.h | ||
| btl_template_frag.c | ||
| btl_template_frag.h | ||
| btl_template_proc.c | ||
| btl_template_proc.h | ||
| btl_template.c | ||
| btl_template.h | ||
| configure.params | ||
| Makefile.am | ||
| netpipe-btl-template.txt | ||
| sample-btl-template.conf | ||