Draft: threads scheduler #4047
Closed
Draft: threads scheduler #4047
Conversation
This file contains hidden or 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
This changes task.Stack and task.Queue to use atomic compare-and-swap operations. With this change, they can also be executed safely from multiple threads/cores. Additionally, the queue is actually LIFO now (not sure what I was thinking before).
|
In addition to the scheduler, the |
|
Yes, |
|
Another important piece is the garbage collector. You need to find a way to pause all other threads while the GC is running. |
|
Close by #4559 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
#2290 must be merged first.
This is a draft of a threads scheduler implementation as a cornerstone of a multi-core implementation.
I can't do it alone. I would love to work together.
See #2446