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 may consume too much time #286

Open
MoonStar2n opened this issue Mar 6, 2024 · 0 comments
Open

lock may consume too much time #286

MoonStar2n opened this issue Mar 6, 2024 · 0 comments

Comments

@MoonStar2n
Copy link

lock is used very frequently in OPAL, and code should not block in OPAL.

lock

However, in the lock_caller function, if cpu not get lock, it will execute the following try to lock code which is in for loop until it get the lock. I think this design may consume too much time in some scenario, OPAL should return immediately whether or not the lock is acquired.
Looking forward for your answer, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant