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.

Sign up for GitHub

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

Jump to bottom

maybe that is wrong #36

Open

kangkangshen opened this issue May 21, 2019 · 1 comment

kangkangshen commented May 21, 2019

The current concurrent scheduling entity of go is not thread, but goroutine, using thread to obtain the lock, the granularity is too large.

Owner

jwells131313 commented Jul 17, 2019

I've probably been imprecise in my words, these recursive locks are based on the stack of the goroutine, not the thread. Thanks for pointing that out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment