osc/ucx: implement rput and rget using ucp_worker_flush_nb #10536
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on a reply by @yosefe in #9580 (comment) it appears that the way osc/ucx implements request based put and get operations might not work well on older networks. This is an attempt at using
ucp_worker_flush_nbinstead to acquire a request that completes once the put or get operations have completed without explicitly posting an atomic operation. I don't know the implementation details ofucp_worker_flush_nbbut it seems like a cleaner solution to me.Fallback to the old method of acquiring a request from an atomic operation is preserved in case
ucp_worker_flush_nbis not available.Some minor fixes to
opal_common_ucx_winfo_flushare also included in this PR.@janjust @yosefe is this the correct use of
ucp_worker_flush_nb?@jotabf fyi this might solve the performance issue you're seeing with
MPI_Rget. I haven't been able to test it on a network like yours though.Signed-off-by: Joseph Schuchart schuchart@icl.utk.edu