[gclist] Page grouping trick

John Levon moz@compsoc.man.ac.uk
Fri, 18 May 2001 20:10:58 +0100 (BST)

On Fri, 18 May 2001, Pekka P. Pirinen wrote:

> > Francois-Rene Rideau <fare@tunes.org> wrote:
> >> Just think about it: if an object might be moved without the address
> >> change having been universally propagated, then you're forced to check
> >> whether the object has moved or not. Hence, a read barrier, either
> >> by conditional forward pointer checking or by inconditional indirection.
> >
> > Yes, exactly.
> You can also use a write barrier, with a replicating collector, see
> <http://www.xanalys.com/software_tools/mm/glossary/r.html#replicating
> .garbage.collector>.


> I think hybrid schemes are also possible, but I don't want to try to
> wrap my head around that on a Friday evening.

coo ... I'll have to think on this one.

> > Does anyone know of a useful paper discussing the trade-offs ?
> > I've been working through the literature, but as I'm sure you all
> > know, it's pretty extensive ;)
> The best review is, as usual, in _Jones and Lins_ <http://www.cs.ukc.
> ac.uk/people/staff/rej/gcbook/gcbook.html>.

I have the book. It's great. It doesn't seem to discuss (very much)
object tables + indirection though ?


p.s. thanks for everyone's useful comments

"Research is not a warm puppy. At least, I hope not."
	- David Rydeheard