Add lock manager #142
Merged
Add lock manager #142
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
The lock-owner data structure |struct lock_owner| describes an object that can own locks, usually a transaction. Lock owners can wait and sleep while requested locks are busy. Lock scheduling and deadlock resolution is handled by an external component.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Each R/W lock now contains a list of waiters. Transactions act as waiters. The lock manager maintains the wait lists for each R/W lock and schedules waiters. This patch set contains all the infrastructure. A lot of tuning and adjustment for the different use cases and access patterns can be build on top of it.