Avoid taking a write lock in RegisteredType::{root,clone,drop}
#7969
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
By moving the registration count into the `Arc`, that is pulling the `Arc` outwards from containing just the `WasmFuncType` to the registration count as well, and turning it into an atomic, we can manipulate the registration count without a write lock. Once that is done, we have the following: * `RegisteredType::root` only needs a read lock, not a write lock. * `RegisteredType::clone`, which used to need a write lock, doesn't need any locking anymore. * `RegisteredType::drop` doesn't need any locking most of the time. The exception is when this is this drop that moves the refcount to zero, in which case grabbing a write lock is still necessary to remove the type from the registry.
fitzgen
force-pushed
the
no-lock-to-clone-drop-registered-type
branch
from
6244e73 to
effb5f0
Compare
alexcrichton
approved these changes
Feb 21, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
By moving the registration count into the
Arc, that is pulling theArcoutwards from containing just theWasmFuncTypeto the registration count as well, and turning it into an atomic, we can manipulate the registration count without a write lock. Once that is done, we have the following:RegisteredType::rootonly needs a read lock, not a write lock.RegisteredType::clone, which used to need a write lock, doesn't need any locking anymore.RegisteredType::dropdoesn't need any locking most of the time. The exception is when this is this drop that moves the refcount to zero, in which case grabbing a write lock is still necessary to remove the type from the registry.