Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MCA variable scope and coll tuned rules file update onto v4.1.x #12928

Merged
merged 8 commits into from
Dec 17, 2024

Conversation

burlen
Copy link

@burlen burlen commented Nov 19, 2024

Pick MCA variable scope and coll tuned rules file update onto v4.1.x

bot:notacherrypick

Burlen Loring added 3 commits November 19, 2024 12:42
Teach the dynamic rules file reader to look for the
alltoall_algorithm_max_requests tuning parameter.  To keep the dynamic rules
file format backward compatible the alltoall_algorithm_max_requests is
optional. When not present in the rule definition the value of the
corresponding MCA variable is used instead.

Resolves open-mpi#12589

Signed-off-by: Burlen Loring <[email protected]>
(cherry picked from commit 33f8c74)
the version identifier is optional but when provided it  must have the
following format and must appear on the first line.`rule-file-version-N`
where N is an unsigned integer. Older versions of the
parser will fall back to fixed decision mechanism when this line is
present. Version 1 is the original format, Version 2 has support for
optional coll_tuned_alltoall_algorithm_max_requests specification.

Signed-off-by: Burlen Loring <[email protected]>
(cherry picked from commit f6387a4)
Changes several variables scope from READONLY to ALL so that they can be set
via MPI_T interface

Signed-off-by: Burlen Loring <[email protected]>
(cherry picked from commit 617e89d)
Copy link

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

d3e0029: fix MCA variable scope in coll han

  • check_cherry_pick: does not include a cherry pick message (did you need to bot:notacherrypick?)

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

Burlen Loring added 5 commits November 20, 2024 13:16
Changes several variables scope from READONLY to ALL so that they can be set
via MPI_T interface

Signed-off-by: Burlen Loring <[email protected]>
(cherry picked from commit 329ea0e)
Changes several variables scope from READONLY to ALL so that they can be set
via MPI_T interface

Signed-off-by: Burlen Loring <[email protected]>
(cherry picked from commit fdf60ac)
Changes several variables scope from READONLY to ALL so that they can be set
via MPI_T interface

Signed-off-by: Burlen Loring <[email protected]>
(cherry picked from commit 44e0436)
Changes several variables scope from READONLY to ALL so that they can be set
via MPI_T interface

Signed-off-by: Burlen Loring <[email protected]>
(cherry picked from commit 75befb8)
Changes several variables scope from READONLY to ALL so that they can be set
via MPI_T interface. Picks up a few instances that were not in main.

bot:notacherrypick

Signed-off-by: bloring <[email protected]>
Copy link

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

f7011c6: fix MCA variable scope in coll han

  • check_cherry_pick: does not include a cherry pick message (did you need to bot:notacherrypick?)

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

@jsquyres
Copy link
Member

We were somewhat hoping that v4.1.7 would be the last release of the v4.1.x series.

Is this functionality absolutely critical and needed in v4.1.x?

@burlen
Copy link
Author

burlen commented Nov 21, 2024

I see. I was not aware. I want them on v4.1.x to be a part of the NVIDIA HPC-X release. HPC-X is the deployment vehicle for several of the systems I use. It sounds like there will be at least one more HPC-X release on v4.1.x branch. #12897. Could these be included?

@bwbarrett
Copy link
Member

We may never do a release, but I'm happy to merge these in. Were these changes a backport from main or something unique to this branch? Just trying to figure out how to make the commit format checker pass.

@burlen
Copy link
Author

burlen commented Dec 16, 2024

I may have missed the boat on getting these into the release. I'm not sure what the schedule for moving to v5 in hpcx is. All but f7011c6 is cherry-picked from main. f7011c6 addresses some issues because some files in v4 branch are not in sync with main

@jsquyres
Copy link
Member

@bwbarrett I don't remember offhand, but the cherry-pick checker may well not look for bot:notacherrypick in commit messages -- it may only look for it in the PR description...? I don't remember why we would have done that, though.

@rhc54
Copy link
Contributor

rhc54 commented Dec 16, 2024

it may only look for it in the PR description...?

Correct - it has to be in the upper description

@bwbarrett
Copy link
Member

Just in the PR description, because bot:notacherrypick doesn't belong in the commit history of the code.

@jsquyres jsquyres merged commit 23b6d34 into open-mpi:v4.1.x Dec 17, 2024
11 of 12 checks passed
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