[WIP] Ownership uses rmaps #334
Draft
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
pqwy
force-pushed
the
ownership-uses-rmaps
branch
from
7589ea5 to
fc33896
Compare
pqwy
force-pushed
the
ownership-uses-rmaps
branch
from
fc33896 to
02504d9
Compare
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.
Adds range-based ownership tracking.
The code itself is good to go. Marking as draft since singleton updates are ~3 times slower than the hash table, making the cn-pKVM-hyp-allocator spec approximately that much slower.
It shows which API to target when vectorising ownership updates.