From now and on, "processor" will mean "an OS thread that's running a GVM", right?


2016-11-08 12:31 GMT+08:00 Marc Feeley <feeley@iro.umontreal.ca>:
.. 
The barrier synchronizations are implemented using a binary tree like structure and time-limited spin-barriers to synchronize a parent processor with its 2 children.  So a barrier takes logarithmic time.

Cool!

Just out of curiosity for nitty-gritty details:

Which processor is the ultimate parent, is this generated at processors initialization, or at each GC? Is it the processor that trigs the GC?

What's the motivation for a tree-like propagation at all, compared for instance with that the processor that trigs GC would do the sync with all other processors, all by itself?


Finally, as it looks now, in what processor will wills be executed, undefined i.e. random?