From: David.Mentre@irisa.fr (David Mentré)
To: Norman Ramsey <nr@eecs.harvard.edu>
Cc: caml-list@inria.fr
Subject: Re: ratio of heap size to live data in Caml GC?
Date: 04 Oct 2000 12:14:28 +0200 [thread overview]
Message-ID: <wd8lmw4kj5n.fsf@parate.irisa.fr> (raw)
In-Reply-To: Norman Ramsey's message of "Tue, 3 Oct 2000 17:50:09 -0400"
Norman Ramsey <nr@eecs.harvard.edu> writes:
> I assume this means the collector is a mark-and-sweep collector?
As far as I have understood, the collector is a combination of a
mark&sweep (at major collection) and of a generation (at minor
collection) collectors.
You'll find a description of this collector, unfortunatly in french, on
this web pages :
http://www.pps.jussieu.fr/Livres/ora/DA-OCAML/book-ora088.html
I *think* you'll find a close description of the actual GC in the
following paper. As I haven't read thise papers, you are on your own :
Damien Doligez, Xavier Leroy. "A concurrent, generational garbage
collector for a multithreaded implementation of ML". Proceedings POPL
93.
http://pauillac.inria.fr/~xleroy/publi/concurrent-gc.ps.gz
This paper presents the design and implementation of a ``quasi
real-time'' garbage collector for Concurrent Caml Light, an
implementation of ML with threads. This two-generation system
combines a fast, asynchronous copying collector on the young
generation with a non-disruptive concurrent marking collector on
the old generation. This design crucially relies on the ML
compile-time distinction between mutable and immutable
objects. (BibTeX reference.)
Hope it helps,
d.
--
David.Mentre@irisa.fr -- http://www.irisa.fr/prive/dmentre/
Opinions expressed here are only mine.
next prev parent reply other threads:[~2000-10-04 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-03 21:50 Norman Ramsey
2000-10-04 10:14 ` David Mentré [this message]
2000-10-05 18:58 ` Chris Quinn
2000-10-08 13:40 Damien Doligez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wd8lmw4kj5n.fsf@parate.irisa.fr \
--to=david.mentre@irisa.fr \
--cc=caml-list@inria.fr \
--cc=nr@eecs.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox