Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lock-free multiple-consumers queues may violate sequential-consistency #13

Open
giucamp opened this issue Nov 17, 2017 · 0 comments
Open
Labels

Comments

@giucamp
Copy link
Owner

giucamp commented Nov 17, 2017

When searching for the first non-dead and non-busy value, consumers should keep track of busy values. After they find a consumable value, they should check whether some of the previously busy values is no more busy, and restart the scan in this case. Currently a value may be consumed after another value even if the first was committed first.

@giucamp giucamp added the bug label Nov 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant