-
Notifications
You must be signed in to change notification settings - Fork 66
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
the scope of spinlock is too large #60
Comments
I remember I spent a while trying to figure how to address this some time ago. |
…outes.c that is on review, things to do: improved the javadoc for new and modified functions.
Updated many comments, solved a couple of concurrence issues and optimized some tree walks.
The revision of #60 is getting out of control and we're already a full week late, so we've decided to postpone it for 3.1.5.
Moving to milestone 3.1.5 because the code's protection against race conditions still doesn't convince me. |
Fixed and collapsed to the master branch; closing. |
the spinlock "bib_session_lock" locks the whole f function that manipulate the sessions and bib, such as ipv6_udp, ipv4_udp, etc, which may cause performance problems in large connections condition.
The text was updated successfully, but these errors were encountered: