From: Philippe Wang <philippe.wang.lists@gmail.com>
To: yoann padioleau <pad.aryx@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] threads, signals, and timeout
Date: Tue, 27 Oct 2009 00:13:22 +0100 [thread overview]
Message-ID: <4d1b2df20910261613l7bd4a7a9yfde623d80c4cf9c5@mail.gmail.com> (raw)
In-Reply-To: <c55bbbbc0910261108l5e59836j1508d69c664bdf8f@mail.gmail.com>
Considering that posix signals are not real-time *anyway*, using them
to programme specific treatments per-thread is hmmm... say a nightmare
! Plus I don't quite see how you could eventually have a non-broken
implementation. Gerd Stolpmann emphasized it if I understood well.
One solution would be to use state variables to check every once in a while.
Or maybe to use "fairthreads" instead, but I guess that the problem is
actually much more complicated than just that.
Well, I thought I had more interesting things to say. I was wrong,
then just my two cents.
Anyways, good luck!
Cheers,
Philippe Wang
On Mon, Oct 26, 2009 at 7:08 PM, yoann padioleau <pad.aryx@gmail.com> wrote:
> Hi,
>
> I would like to create different threads where each thread do some
> computation and are subject to different
> timeout. Without threads I usually use Unix.alarm with a SIGALARM
> handler that just raise a Timeout exception
> and everything works fine, but when I try to do something similar with
> threads it does not work
> because apparently the Unix.alarm done in one thread override the
> Unix.alarm done in another
> thread. I had a look at thread.mli but was not able to find anything
> related to timeout.
> Is there a way to have multiple timeout and multiple threads at the same time ?
>
> Here is a program that unforunately get the first timeout, but not the second :(
>
>
> (*
> ocamlc -g -thread unix.cma threads.cma signals_and_threads.ml
> *)
>
> exception Timeout
>
> let mytid () =
> let t = Thread.self () in
> let i = Thread.id t in
> i
>
> let set_timeout () =
>
> Sys.set_signal Sys.sigalrm
> (Sys.Signal_handle (fun _ ->
> prerr_endline "Time is up!";
> print_string (Printf.sprintf "id: %d\n" (mytid()));
> raise Timeout
> ));
>
> ignore(Unix.alarm 1);
> ()
>
>
> let main =
> let t1 =
> Thread.create (fun () ->
> set_timeout ();
> print_string (Printf.sprintf "t1 id: %d\n" (mytid()));
>
> let xs = [1;2;3] in
> while(true) do
> let _ = List.map (fun x -> x + 1) xs in
> ()
> done;
> ()
> ) ()
> in
>
> let t2 =
> Thread.create (fun () ->
> set_timeout ();
> print_string (Printf.sprintf "t2 id: %d\n" (mytid()));
>
> let xs = [1;2;3] in
> while(true) do
> let _ = List.map (fun x -> x + 1) xs in
> ()
> done;
> ()
> ) ()
> in
> Thread.join t1;
> Thread.join t2;
> ()
>
> ------------------
>
>
>
>
> Here is the output
> Time is up!
> t2 id: 2
> t1 id: 1
> id: 1
> Thread 1 killed on uncaught exception Signals_and_threads.Timeout
> .... <the program loops, meaning the second thread never received its timeout
>
prev parent reply other threads:[~2009-10-26 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 18:08 yoann padioleau
2009-10-26 18:36 ` [Caml-list] " Till Varoquaux
2009-10-26 19:06 ` yoann padioleau
2009-10-26 22:14 ` Gerd Stolpmann
2009-10-27 10:01 ` Gabriel Kerneis
2009-10-26 23:13 ` Philippe Wang [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=4d1b2df20910261613l7bd4a7a9yfde623d80c4cf9c5@mail.gmail.com \
--to=philippe.wang.lists@gmail.com \
--cc=caml-list@inria.fr \
--cc=pad.aryx@gmail.com \
/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