3903009b8b
protocol over the MX BTL. Now, we have only one matching, the one in Open MPI. The problem is that when the unexpected handler is triggered, not all the message is on the host memory. In the best case we get one MX fragment (internal MX fragment), in the worst we get NULL. The only way to fit this with the design of the PML is to force the eager protocol at the MX internal fragment size, and to limit the send/receive protocol at the same size. Tests show the outcome is not far from optimal (if the pipeline depth is increased a little bit). Set MX_PIPELINE_LOG in order to allow MX to use internal fragments of 4K. This commit was SVN r12930. |
||
---|---|---|
.. | ||
btl_mx_component.c | ||
btl_mx_endpoint.c | ||
btl_mx_endpoint.h | ||
btl_mx_frag.c | ||
btl_mx_frag.h | ||
btl_mx_proc.c | ||
btl_mx_proc.h | ||
btl_mx.c | ||
btl_mx.h | ||
configure.m4 | ||
configure.params | ||
Makefile.am |