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

Only scheduler 0 can initiate shutdown #4543

Merged
merged 1 commit into from
Nov 24, 2024

Conversation

dipinhora
Copy link
Contributor

prior to this commit, every scheduler thread tried to initiate the shutdown CNF/ACK process if it was unable to steal from another scheduler thread even through in practice only scheduler 0 could ever initiate shutdown since it is the only one that receives ACK/BLOCK/SUSPEND messages and has enough information.

This commit changes things so that it is explicit that only scheduler 0 initiates the shutdown CNF/ACK process.

prior to this commit, every scheduler thread tried to initiate
the shutdown CNF/ACK process if it was unable to `steal` from
another scheduler thread even through in practice only scheduler
0 could ever initiate shutdown since it is the only one that
receives ACK/BLOCK/SUSPEND messages and has enough information.

This commit changes things so that it is explicit that only
scheduler 0 initiates the shutdown CNF/ACK process.
@ponylang-main ponylang-main added the discuss during sync Should be discussed during an upcoming sync label Nov 22, 2024
@SeanTAllen SeanTAllen merged commit 5e56388 into ponylang:main Nov 24, 2024
23 checks passed
@ponylang-main ponylang-main removed the discuss during sync Should be discussed during an upcoming sync label Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants