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

Revert "rt: refactor current-thread scheduler (#4377)" #4394

Merged
merged 1 commit into from
Jan 11, 2022

Conversation

carllerche
Copy link
Member

This reverts commit cc8ad36, which caused hyper's tests to fail.

@github-actions github-actions bot added the R-loom Run loom tests on this PR label Jan 11, 2022
@carllerche carllerche merged commit 867f137 into master Jan 11, 2022
@carllerche carllerche deleted the revert-rt-refactor- branch January 11, 2022 19:57
@taiki-e taiki-e mentioned this pull request Jan 11, 2022
carllerche added a commit that referenced this pull request Jan 11, 2022
carllerche added a commit that referenced this pull request Jan 12, 2022
Re-applies #4377 and fixes the bug resulting in Hyper's double panic.

Revert: #4394

Original PR:

This PR does some refactoring to the current-thread scheduler bringing it closer to the structure of the
multi-threaded scheduler. More specifically, the core scheduler data is stored in a Core struct and that
struct is passed around as a "token" indicating permission to do work. The Core structure is also stored
in the thread-local context.

This refactor is intended to support #4373, making it easier to track counters in more locations in the
current-thread scheduler.

I tried to keep commits small, but the "set Core in thread-local context" is both the biggest commit and
the key one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R-loom Run loom tests on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants