Re: [rvm-research] Why both insertion and deletion barrier in sync1/2 phases of on-the-fly Garbage collector are needed?

See section 16.5, p.328-9, of the Garbage Collection Handbook. It's 
because phase changes are asynchronous, and different mutator threads 
are in different states. A deletion barrier alone is insufficient.

Richard

> Lokesh Gidra <mailto:[email protected]>
> 6 July 2016 at 21:03
> Hi,
>
> Given that the write barrier and object allocation are supposed to be 
> atomic wrt. handshakes, why does an SATB based on-the-fly 
> implementation (like the famous DLG from POPl'94 paper) need to use 
> both, insertion and deletion barriers during sync1 and sync2 phases? 
> Won't just using deletion barrier suffice?
>
>
> Kind Regards,
> Lokesh
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape
> _______________________________________________
> Jikesrvm-researchers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers

------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape

_______________________________________________
Jikesrvm-researchers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers