From: Julien Cristau <julien.cristau@ens-lyon.fr>
To: caml-list@inria.fr
Cc: david.baelde@ens-lyon.org
Subject: mmap() and strings
Date: Wed, 8 Dec 2004 21:04:59 +0100 [thread overview]
Message-ID: <20041208200458.GC1840@ens-lyon.fr> (raw)
Hello list,
I'm wondering if somebody has an idea for the following problem:
I'm working on a program which manipulates a buffer. A writer process
regularly changes this buffer, and reader processes have to work on it
after each change. Currently, the buffer is a string and is passed to
the readers trough pipes. However, this is costly because the buffer is
copied many times at each iteration.
We thought we could use mmap(2), but there seems to be no easy solution
to mmap() a memory region and treat it as a string in ocaml. Does
anybody have a better idea how we could solve this problem without
copying the buffer?
Julien
next reply other threads:[~2004-12-08 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 20:04 Julien Cristau [this message]
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
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=20041208200458.GC1840@ens-lyon.fr \
--to=julien.cristau@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).