From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
To: Damien Doligez <damien.doligez@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Thread in OCaml
Date: Fri, 16 Apr 2004 21:03:47 -0400 [thread overview]
Message-ID: <40808273.2060604@univ-savoie.fr> (raw)
In-Reply-To: <432746EE-8FC1-11D8-806C-00039310CAE8@inria.fr>
>
> 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
prev parent reply other threads:[~2004-04-16 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 10:30 Christophe Raffalli
2004-04-16 11:23 ` Daniel Bünzli
2004-04-16 16:15 ` Damien Doligez
2004-04-17 1:03 ` Christophe Raffalli [this message]
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=40808273.2060604@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.fr \
--cc=caml-list@inria.fr \
--cc=damien.doligez@inria.fr \
/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;
as well as URLs for NNTP newsgroup(s).