> 
> Allocating can call the GC, and the GC can move values around, which
> invalidates pointers.  Even read-only access to the heap is impossible
> during the GC.

I beleived that only the compaction Gc moved value.
But I guess that value are mover from the minor heap to the major heap ...

>> If you think a typical Caml program spend 20% of time during 
>> allocation(which include GC) then 5 threads could run concurrently on 
>> 5 CPUs with some speedup (up to 5 times in the best case).
> 
> 
> If only it was so easy to make a good concurrent GC...

Will there be one for OCaml
-- 
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex

tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
---------------------------------------------
IMPORTANT: this mail is signed using PGP/MIME
At least Enigmail/Mozilla, mutt or evolution
can check this signature
---------------------------------------------

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners