From: Shivkumar Chandrasekaran <shiv@ece.ucsb.edu>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Stopping and continuing GC
Date: Fri, 17 Aug 2007 09:44:14 -0700 [thread overview]
Message-ID: <B59A0D7C-FFE1-4393-A5BA-80EBD934A538@ece.ucsb.edu> (raw)
In-Reply-To: <20070817.100453.94562786.garrigue@math.nagoya-u.ac.jp>
On Aug 16, 2007, at 6:04 PM, Jacques Garrigue wrote:
> This looks like a misunderstanding.
> You cannot stop the GC in ocaml: it will be triggered as soon as the
> young heap is full anyway.
> What lablGTK does is turning off compaction, which is a rather new
> feature of the GC (didn't exist when lablgtk was first written), which
> moves around objects in the old generation, which would break some
> assumptions in the code. As indicated, you can still call compaction
> explicitly, a simple way being to call Gc.major once in a
> while (using a timer for instance), as it will do compaction too when
> needed.
When I first read it I thought I got it... If I read you correctly,
you are saying that lablGTK has tuned off compaction (somehow), but
if I manually call Gc.major I can have it done. But, you also say
that Gc itself is not turned off. But, I thought Gc.major was an
intrinsic part of the gc cycle. Which would imply that compaction
would be called anyway, even if I did not call Gc.major explicitly.
Are you saying that the "major sweeps" (whatever Gc.major does) are
also turned off....
OTOH, the manual says:
> If max_overhead >= 1000000, compaction is never triggered.
If lablGTK has set this, then presumably calling Gc.major will have
no impact.
Thanks for any clarifications.
--shiv--
next prev parent reply other threads:[~2007-08-17 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 22:14 Shivkumar Chandrasekaran
2007-08-17 1:04 ` [Caml-list] " Jacques Garrigue
2007-08-17 14:05 ` Markus Mottl
2007-08-17 15:00 ` Richard Jones
2007-08-17 16:44 ` Shivkumar Chandrasekaran [this message]
2007-08-17 19:03 ` Richard Jones
2007-08-18 0:07 ` Jacques GARRIGUE
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=B59A0D7C-FFE1-4393-A5BA-80EBD934A538@ece.ucsb.edu \
--to=shiv@ece.ucsb.edu \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
/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).