From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id JAA15513; Tue, 9 Oct 2001 09:23:18 +0200 (MET DST) Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id JAA15325 for ; Tue, 9 Oct 2001 09:23:17 +0200 (MET DST) Received: from lachesis.inria.fr (lachesis.inria.fr [128.93.52.5]) by concorde.inria.fr (8.11.1/8.10.0) with ESMTP id f997NF516344; Tue, 9 Oct 2001 09:23:15 +0200 (MET DST) Received: (from lefessan@localhost) by lachesis.inria.fr (8.11.3/8.11.3) id f997Ne209481; Tue, 9 Oct 2001 09:23:40 +0200 X-Authentication-Warning: lachesis.inria.fr: lefessan set sender to fabrice.le_fessant@inria.fr using -f From: Fabrice Le Fessant MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15298.42491.228801.381507@lachesis.inria.fr> Date: Tue, 9 Oct 2001 09:23:39 +0200 (CEST) To: "Don Syme" Cc: Subject: Re: [Caml-list] Memory mapped values References: X-Mailer: VM 6.75 under Emacs 20.7.1 Reply-To: fabrice.le_fessant@inria.fr Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk In the CDK, you will find a very small library "mmap" closed to what you are talking about. The idea is to output the values in the file as if they were in memory, so that the file can be directly mapped in memory, and the values directly used by Ocaml. The library has not yet being tested a lot. Of course, these values cannot be collected by the garbage collector, nor should be mutable. However, there is a big (unsolved yet) problem with compaction. Another problem is the size of the pages bitmap used by the garbage collector, since the file might be mapped very far from the main heap. Regards, - Fabrice ------------------- Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr