From: David Baelde <david.baelde@ens-lyon.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] mmap() and strings
Date: Thu, 09 Dec 2004 11:32:06 +0100 [thread overview]
Message-ID: <41B829A6.7040201@ens-lyon.fr> (raw)
In-Reply-To: <20041209.104204.95951378.garrigue@math.nagoya-u.ac.jp>
Hello and thank you for this precise (and impressive) answer,
(I'm working together with Julien)
But actually, we need also to get a bigarray from string. So the writer
could get a string as usual, copy it once in a shared bigarray, and then
let the readers read it, without any more copies.
Anyway, I'm also quite afraid of including suck black magic in our
project ;) We're OK for writing some C, we already did. Maybe it would
be easier than Obj.Magic stuff.
Avoiding copies is our goal, but it seems impossible to get a string of
which Caml doesn't own the blocks, in order to make a mmaped mem area
corresponding to many strings in the writer/readers processes.
--
David
prev parent reply other threads:[~2004-12-09 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 20:04 Julien Cristau
2004-12-08 20:24 ` [Caml-list] " Basile STARYNKEVITCH
2004-12-08 20:50 ` Julien Cristau
2004-12-09 1:09 ` Jacques Garrigue
2004-12-09 1:42 ` Jacques Garrigue
2004-12-09 10:32 ` David Baelde [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=41B829A6.7040201@ens-lyon.fr \
--to=david.baelde@ens-lyon.fr \
--cc=caml-list@inria.fr \
--cc=david.baelde@ens-lyon.org \
/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).