From: David Thomas <david_hd@yahoo.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Fork-friendly GC
Date: Mon, 2 Jul 2007 18:42:57 -0700 (PDT) [thread overview]
Message-ID: <110525.65902.qm@web30502.mail.mud.yahoo.com> (raw)
In-Reply-To: <c1490a380707021046y214ad63cna6796413ccf1676@mail.gmail.com>
It seems to me that an incomplete but simple solution
is to stop garbage collection on the shared heaps, and
allocate new objects on fresh pages, unique to each
process. This does, of course, mean that some objects
which should be freed don't get freed, but this seems
a price worth paying - we're only wasting some of the
memory instead of all of the memory, and we're not
taking nearly as much time.
Perhaps it's even possible to detect when we've
written to one of these pages, and re-add them to the
heap when the OS has already copied them for us, but
that's getting more complicated than necessary for a
first pass...
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
prev parent reply other threads:[~2007-07-03 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 14:00 Jon Harrop
2007-07-02 17:46 ` [Caml-list] " Tom
2007-07-03 1:42 ` David Thomas [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=110525.65902.qm@web30502.mail.mud.yahoo.com \
--to=david_hd@yahoo.com \
--cc=caml-list@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).