If I understand this correctly, it basically has the second thread wait until the first one experiences a hardware interrupt, which implicitly synchronizes memory. This avoids the first thread from needing any synchronization primitives that would slow it down.
If I understand this correctly, it basically has the second thread wait until the first one experiences a hardware interrupt, which implicitly synchronizes memory. This avoids the first thread from needing any synchronization primitives that would slow it down.
Oh boy this is a cool blog post. Encourage everyone to read it.
There are many more cool posts on that blog.
"GC"?
Garbage collection. It's in the leading paragraph of the article so I can see why it's easy to miss.