Really cool, learnt a lot! Adding a demonstration (and the associated visualization) really made it click to understand work-stealing and the effects of locality wrt global and local runqueues. Thank you so much for this!
OS threads don't directly access the queue, you don't have any control over them. They are green threads or user-managed threads totally by go runtime.
4:30 is not true, a proccesor core can have multiple hardware threads. So Logical Processors is actually bind to vircutal cores and virtual cores are actually bind to hardware threads. So 1 hardware thread == 1 machine or 1 os thread
Very crisp talk. I wondered how fair the scheduling was, but never learned it. This talk answered all my scheduling questions, and more.
Great exploration of the Go scheduler! Thank you, Madhav.
Really cool, learnt a lot! Adding a demonstration (and the associated visualization) really made it click to understand work-stealing and the effects of locality wrt global and local runqueues.
Thank you so much for this!
Thank you! ❤️
Well explained!!! That was really helpful.. Thanks
This was awesome!!! Thank you
Awesome!
OS threads don't directly access the queue, you don't have any control over them.
They are green threads or user-managed threads totally by go runtime.
4:30 is not true, a proccesor core can have multiple hardware threads. So Logical Processors is actually bind to vircutal cores and virtual cores are actually bind to hardware threads. So 1 hardware thread == 1 machine or 1 os thread
Thanks for these insights. Out of curiosity, why OS/kernel threads are abbreviated `M`?
machine (M)
нохчи кхочур буй те кхуз
presentation is very poorly made and his accent is hard to follow + he is switching thoughts flow too fast... thanks for trying thou