From: "Bauer, Christoph" <bauerchristoph@siemens.com>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] memory mapped files with bigarray on windows
Date: Thu, 18 Sep 2014 08:04:53 +0000 [thread overview]
Message-ID: <B604D632D4692C45A95E5EB6E3E0FFF201AD77BF@DEKOMMBX002.net.plm.eds.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
Dear All,
my program maps several blocks of a file into memory with Bigarray.Array1.map_file for writing.
Finally the file handle is closed with Unix.close.
On local files system everything works as expected. But if the file is on a network drive,
the resulting file is after the close still locked [1] and it contains just zeros.
My workaround is, to call Gc.full_major() before the close. Then all remaining bigarrays are
finalized (the finalizer calls caml_ba_unmap_file(), see bigarray_stubs.c).
Calling Gc.full_major () is somewhat dissatisfying. But I’m not sure how it could be solved more cleanly.
I would expect that Unix.close should unmap all remaining views of the file. But Unix.close knows nothing
about the bigarray mapping.
Maybe a special Bigarray.unmap is the solution.
Does anyone has a better idea?
Thanks,
Christoph Bauer
[1] You can’t delete it in the windows explorer.
-----------------
Siemens Industry Software GmbH & Co. KG; Anschrift: Franz-Geuer-Str. 10, 50823 Köln;
Kommanditgesellschaft: Sitz der Gesellschaft: Köln; Registergericht: Amtsgericht Köln, HRA 28227;
Geschäftsführung und persönlich haftender Gesellschafter: Siemens Industry Software Management GmbH;
Geschäftsführer: Urban August, Daniel Trebes; Sitz der Gesellschaft: Köln; Registergericht: Amtsgericht Köln, HRB 70858
[-- Attachment #2: Type: text/html, Size: 3499 bytes --]
next reply other threads:[~2014-09-18 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 8:04 Bauer, Christoph [this message]
2014-09-18 8:24 ` Gabriel Scherer
2014-09-18 11:09 ` Gerd Stolpmann
2014-09-18 14:41 ` AW: " Bauer, Christoph
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=B604D632D4692C45A95E5EB6E3E0FFF201AD77BF@DEKOMMBX002.net.plm.eds.com \
--to=bauerchristoph@siemens.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