From: David Brown <caml-list@davidb.org>
To: Vincenzo Ciancia <vincenzo_mlRE.MOVE@yahoo.it>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] non-blocking Unix.*stat functions?
Date: Thu, 28 Oct 2004 14:45:04 -0700 [thread overview]
Message-ID: <20041028214504.GA1279@old.davidb.org> (raw)
In-Reply-To: <200410282206.35089.vincenzo_mlRE.MOVE@yahoo.it>
On Thu, Oct 28, 2004 at 10:06:31PM +0200, Vincenzo Ciancia wrote:
> in the process of building a multithreaded and up-to-date binding to the
> fuse (filesystem in userspace) library, I just noticed that unix.stat
> and friends are blocking operations (in the sense that they block other
> threads). Binding their unix counterparts using a [blocking] tag in
> camlidl would be easy, but could this perhaps be fixed in the standard
> library?
Well, in "ordinary" filesystems, stat and friends don't generally take very
much time, which is probably why they aren't blocking.
It wouldn't be hard to make them blocking, but you would have to copy the
pathname strings (since they could move while blocked).
Dave
next prev parent reply other threads:[~2004-10-28 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 20:06 Vincenzo Ciancia
2004-10-28 21:45 ` David Brown [this message]
2004-10-29 8:07 ` [Caml-list] " Vincenzo Ciancia
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=20041028214504.GA1279@old.davidb.org \
--to=caml-list@davidb.org \
--cc=caml-list@inria.fr \
--cc=vincenzo_mlRE.MOVE@yahoo.it \
/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).