ucs_async_context_init() call
The call allocates asynchronous context. It is only UCS call that we have to issue in order to program UCT apps. Shell we move it to UCT ?
Done - No need to move.
Definition of APIs for the checkpoint mechanism: ucp_flush_all(), ucp_abort_message() ?
Work in progress - Checkpoint and restart design
Multi-fabrics support (dual home, one leg connected to one fabric1, another to fabric2)
Multi-rail (both leg connected to same fabric)
Thread safety
The thread context lock is located on a work and this is not optimal location for the mutex, since the access to the lock will require at least two dereferences ep->iface->worker