News for hackers. Stuff that matters.

A comment on Go GC: Prioritizing low latency and simplicity.

Re:Go GC: Prioritizing low latency and simplicity by qznc on Tuesday September 01, 2015 @03:34AM (#10151166)
> Maintaining this invariant is the job of the write barrier, which is a small function run by the mutator whenever a pointer in the heap is modified.

Synchronization whenever a heap pointer is changed? That does not sound like "low latency".

[ Parent | on HN ]
Re:Go GC: Prioritizing low latency and simplicity by dfox on Tuesday September 01, 2015 @03:49AM (#10151202)
In case of GC terminology "barrier" simply means that some kind of hook is run on read or write of pointer, it does not necessarily imply barrier in the caching or synchronization sense.

Typical implementation of write barrier involves adding item to some kind of thread-local queue.

[ Parent | on HN ]