Skip to content

v6.0.x: coll/ucc: enable asymmetric datatype check in UCC without OMPI fallback #13658

Open
QiaoK wants to merge 1 commit intoopen-mpi:v6.0.xfrom
QiaoK:ompi_ucc_dt_check_6.0
Open

v6.0.x: coll/ucc: enable asymmetric datatype check in UCC without OMPI fallback #13658
QiaoK wants to merge 1 commit intoopen-mpi:v6.0.xfrom
QiaoK:ompi_ucc_dt_check_6.0

Conversation

@QiaoK
Copy link
Contributor

@QiaoK QiaoK commented Jan 16, 2026

This change enables UCC to perform asymmetric datatype checks internally for gather, gatherv, scatter, and scatterv operations. This feature is only available in UCC 1.8 or greater.

The motivation for this change is to avoid scenarios where a subset of processes fallback to OMPI while other processes proceed to UCC when asymmetric datatypes are supplied. By letting UCC handle the datatype asymmetry check, UCC can signal all processes to fallback when necessary, ensuring consistent collective operation execution across all ranks.

@QiaoK QiaoK added this to the v6.0.0 milestone Jan 16, 2026
@QiaoK QiaoK requested a review from janjust January 16, 2026 15:26
@QiaoK QiaoK self-assigned this Jan 16, 2026
@QiaoK QiaoK added the bug label Jan 16, 2026
@QiaoK QiaoK force-pushed the ompi_ucc_dt_check_6.0 branch from a5ec227 to 946266f Compare January 17, 2026 03:40
@janjust janjust changed the title coll/ucc: enable asymmetric datatype check in UCC without OMPI fallback v6.0.x: coll/ucc: enable asymmetric datatype check in UCC without OMPI fallback Jan 17, 2026
Copy link
Member

@jsquyres jsquyres left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this not a cherry pick of #13656?

If it actually is a cherry-pick -- even if there was some back-porting necessary -- then this PR should not be marked as notacherrypick and the commit message should include the cherry pick message.

@QiaoK QiaoK force-pushed the ompi_ucc_dt_check_6.0 branch from 946266f to d195d93 Compare January 19, 2026 20:39
@QiaoK
Copy link
Contributor Author

QiaoK commented Jan 19, 2026

Is this not a cherry pick of #13656?

If it actually is a cherry-pick -- even if there was some back-porting necessary -- then this PR should not be marked as notacherrypick and the commit message should include the cherry pick message.

I updated the commit with cherry-pick message.

@jsquyres jsquyres changed the title v6.0.x: coll/ucc: enable asymmetric datatype check in UCC without OMPI fallback v6.0.x: coll/ucc: enable asymmetric datatype check in UCC without OMPI fallback Jan 20, 2026
@jsquyres jsquyres force-pushed the ompi_ucc_dt_check_6.0 branch from d195d93 to dbd6a04 Compare January 20, 2026 15:19
@jsquyres
Copy link
Member

I updated the commit with cherry-pick message.

Thanks.

Something is still wrong with our CI, though -- it should fail the git commit check if the commit you cherry picked from is not yet merged in its source branch (i.e., main). Put simply: we can't merge this PR (or #13657) until the main PR is merged (#13656). CI is supposed to enforce that, but apparently that check is not working properly.

This change enables UCC to perform asymmetric datatype checks internally
for gather, gatherv, scatter, and scatterv operations. This feature is
only available in UCC 1.8 or greater.

The motivation for this change is to avoid scenarios where a subset of
processes fallback to OMPI while other processes proceed to UCC when
asymmetric datatypes are supplied. By letting UCC handle the datatype
asymmetry check, UCC can signal all processes to fallback when necessary,
ensuring consistent collective operation execution across all ranks.

Signed-off-by: Qiao Kang <qkang@nvidia.com>
(cherry picked from commit ca0ef29)
@QiaoK QiaoK force-pushed the ompi_ucc_dt_check_6.0 branch from dbd6a04 to cf7c51f Compare January 24, 2026 02:39
@github-actions
Copy link

Hello! The Git Commit Checker CI bot found a few problems with this PR:

cf7c51f: coll/ucc: enable asymmetric datatype check in UCC ...

  • check_cherry_pick: contains a cherry pick message that refers to a commit that exists, but is in an as-yet unmerged pull request: ca0ef29

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

1 similar comment
@github-actions
Copy link

Hello! The Git Commit Checker CI bot found a few problems with this PR:

cf7c51f: coll/ucc: enable asymmetric datatype check in UCC ...

  • check_cherry_pick: contains a cherry pick message that refers to a commit that exists, but is in an as-yet unmerged pull request: ca0ef29

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

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.

2 participants