feat: scheduler plugins (3/): add topology spread constraints plugin logic #437
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zhiying-lin
approved these changes
Jul 20, 2023
| }, | ||
| }, | ||
| { | ||
| name: "multiple domains, different counts, separate special counts", |
There was a problem hiding this comment.
hmm, i did not get what's the "separate special" counts. could you please explain it a little bit?
There was a problem hiding this comment.
The separate special counts refer to the smallest, second smallest, and largest counts the counter tracks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of your changes
This PR is part of the PRs that implement the in-tree scheduler framework plugins.
It features some scheduling logic for the topology spread constraints plugin.
I have:
make reviewableto ensure this PR is ready for review.How has this code been tested
Special notes for your reviewer
To control the size of the PR, certain unit tests are not checked in; they will be sent in a separate PR.