Skip to content

Conversation

@devreal
Copy link
Contributor

@devreal devreal commented Aug 15, 2022

This PR brings the changes from #10642 and #10658 to 5.0.x:

  1. Revert a commit that was erroneous on main but correct in 5.0.x in osc/ucx: implement rput and rget using ucp_worker_flush_nb [v5.0.x]  #10554. For consistency purposes, the backport of the faulty commit is reverted and the corrected commit applied.
  2. Bring in a follow-up fixup to ensure proper release of requests in error branches. This again was missing from the master PR.

bot:notacherrypick

Fallback to the old method of acquiring a request from an atomic operation
is preserved. Some networks might provide better performance
if the request-based operations do not rely on atomic operations.

Some minor fixes to opal_common_ucx_winfo_flush included in this
commit.

Signed-off-by: Joseph Schuchart <schuchart@icl.utk.edu>
(cherry picked from commit e7d8cc7)
… error paths

Signed-off-by: Joseph Schuchart <schuchart@icl.utk.edu>
(cherry picked from commit c66aab0)
@devreal devreal force-pushed the osc-ucx-rputget-flushnb-main-fixup-5.0.x branch from 4c18805 to 9fe00eb Compare August 15, 2022 19:32
@devreal
Copy link
Contributor Author

devreal commented Aug 15, 2022

@jsquyres what is the right way to revert commits on release branches? Should I specify the not-a-cherrypick tag?

Error: * 7263c5a: Revert "osc/ucx: implement rput and rget using ucp...
Error: * check_cherry_pick: does not include a cherry pick message (did you need to bot:notacherrypick?)

@jsquyres
Copy link
Member

jsquyres commented Aug 15, 2022

@jsquyres what is the right way to revert commits on release branches? Should I specify the not-a-cherrypick tag?

Yes: bot:notacherrypick in the body of the PR (it doesn't need to be in the commit message -- just the first/initial description on the PR)

@hppritcha
Copy link
Member

bot:ompi:retest

@awlauria
Copy link
Contributor

@janjust please review

@awlauria awlauria merged commit 78d3d9d into open-mpi:v5.0.x Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants