caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Markus Mottl <markus@oefai.at>
To: OCaml <caml-list@inria.fr>
Subject: [Caml-list] "noalloc" + enter/leave blocking section - safe?
Date: Mon, 2 Aug 2004 12:43:49 +0200	[thread overview]
Message-ID: <20040802104349.GA6997@fichte.ai.univie.ac.at> (raw)

Hi,

one important question: is it safe to use "noalloc" with
C-functions that contain calls to "caml_enter_blocking_section" and
"caml_leave_blocking_section" to allow other POSIX-treads?

I have the following external function:

  (** Synchronize all filesystem buffers with disk. *)
  external sync : unit -> unit = "unix_sync" "noalloc"

It is implemented as follows:

  CAMLprim value unix_sync()
  {
    caml_enter_blocking_section();
      sync();
    caml_leave_blocking_section();
    return Val_unit;
  }

When removing the "noalloc" attribute, I cannot reproduce the problem
(crash) reported in bug report #3019 anymore, but I'm not sure whether
this is just a coincidence.

Of course, functions with this attribute shouldn't allocate anything on
the OCaml-heap or throw exceptions.  But I thought that context-switches
would be safe?

Best regards,
Markus

-- 
Markus Mottl          http://www.oefai.at/~markus          markus@oefai.at

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


             reply	other threads:[~2004-08-02 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 10:43 Markus Mottl [this message]
2004-08-02 15:15 ` Markus Mottl
2004-08-02 15:34   ` Jere Sanisalo
2004-08-02 15:49     ` Falk Hueffner
2004-08-02 16:02       ` Richard Jones
2004-08-02 16:32       ` Markus Mottl
2004-08-02 16:39         ` Falk Hueffner

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=20040802104349.GA6997@fichte.ai.univie.ac.at \
    --to=markus@oefai.at \
    --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;
as well as URLs for NNTP newsgroup(s).