From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from discorde.inria.fr (discorde.inria.fr [192.93.2.38]) by yquem.inria.fr (Postfix) with ESMTP id 9CCDEBC8A for ; Fri, 1 Dec 2006 10:19:46 +0100 (CET) Received: from furbychan.cocan.org (furbychan.cocan.org [80.68.91.176]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id kB19JiWk028763 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 1 Dec 2006 10:19:46 +0100 Received: from rich by furbychan.cocan.org with local (Exim 3.35 #1 (Debian)) id 1Gq4YO-0007h6-00; Fri, 01 Dec 2006 09:19:32 +0000 Date: Fri, 1 Dec 2006 09:19:32 +0000 To: Neal Wang Cc: j h woodyatt , The Caml Trade Subject: Re: [Caml-list] Can GC be BLOCKed? Message-ID: <20061201091932.GA29517@furbychan.cocan.org> References: <1965df800611291633q4f615df5qaa43dc967ba87d56@mail.gmail.com> <1FB91514-18D1-4502-AF67-C1003EB8636B@mac.com> <1965df800611301607g330f5517saeba25d40c3321ca@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1965df800611301607g330f5517saeba25d40c3321ca@mail.gmail.com> User-Agent: Mutt/1.5.9i From: Richard Jones X-Miltered: at discorde with ID 456FF3B1.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; allocates:01 blog:98 blog:98 heap:01 heap:01 wrote:01 minor:01 minor:01 caml-list:01 data:02 data:02 external:02 module:03 solved:04 solved:04 On Thu, Nov 30, 2006 at 04:07:51PM -0800, Neal Wang wrote: > Thanks for your help. But your solution only work for a function > which allocates > memory of fixed size. Unfortunately, the atomic function, which > cannot be interrupted by GC, read input data from external channels > and the memory needed to store the input data is not determined ahead. > The official interface of GC doesn't not provide a way to stop GC. Is > there a backdoor such that we can use to stop GC? I can't see how this would work. The minor heap is a fixed size (32K or something) and when this is used up, you _have_ to do a minor collection. Can you tell us what the problem is that you're trying to solve? I've only seen two cases where I'd want to stop the GC from running: (1) During quasi real-time operations (eg. a single frame in a game) -- this can be solved by making the heap large enough and running the GC at scheduled points. (2) When the heap is larger than physical RAM -- this is solved using our 'Ancient' module. Rich. -- Richard Jones, CTO Merjis Ltd. Merjis - web marketing and technology - http://merjis.com Internet Marketing and AdWords courses - http://merjis.com/courses - NEW! Merjis blog - http://blog.merjis.com - NEW!