[gambit-list] parallel GC

Adam adam.mlmb at gmail.com
Wed Nov 9 22:28:59 EST 2016


>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 at 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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.iro.umontreal.ca/pipermail/gambit-list/attachments/20161110/f448aacb/attachment.htm>


More information about the Gambit-list mailing list