runtime (gc_blocks.go): implement thread-local stack scanning#5113
Draft
niaow wants to merge 1 commit intotinygo-org:devfrom
Draft
runtime (gc_blocks.go): implement thread-local stack scanning#5113niaow wants to merge 1 commit intotinygo-org:devfrom
niaow wants to merge 1 commit intotinygo-org:devfrom
Conversation
This change allows all thread stacks to be scanned in parallel. Each thread marks all objects reachable from its stack, using a thread-local scan list. The marking code now uses atomics to access GC metadata. If multiple threads try to mark the same object, the first one will responsible for scanning it.
Member
Author
|
Leaving this as a draft because it is still pretty inefficient and needs more work. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This change allows all thread stacks to be scanned in parallel. Each thread marks all objects reachable from its stack, using a thread-local scan list.
The marking code now uses atomics to access GC metadata. If multiple threads try to mark the same object, the first one will responsible for scanning it.