From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id NAA28642; Wed, 14 Apr 2004 13:45:41 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id NAA29678 for ; Wed, 14 Apr 2004 13:45:40 +0200 (MET DST) Received: from mail3.epfl.ch (mail3.epfl.ch [128.178.50.19]) by nez-perce.inria.fr (8.12.10/8.12.10) with SMTP id i3EBkejq019171 for ; Wed, 14 Apr 2004 13:46:40 +0200 Received: (qmail 26042 invoked by uid 107); 14 Apr 2004 11:45:38 -0000 Received: from mailav2.epfl.ch (HELO mailav2) (128.178.50.191) by mail3.epfl.ch with SMTP; 14 Apr 2004 11:45:38 -0000 Received: From mail0.epfl.ch ([128.178.50.57]) by mailav2 (WebShield SMTP v4.5 MR1a P0803.345); id 1081943344973; Wed, 14 Apr 2004 13:49:04 +0200 Received: from lamp2priv1.epfl.ch (128.178.154.46) by mail0.epfl.ch (AngelmatoPhylax SMTP proxy); Wed, 14 Apr 2004 13:45:38 +0200 In-Reply-To: <407D0289.5090807@univ-savoie.fr> References: <407B9D6F.70800@univ-savoie.fr> <20040413194854.GB27613@davidb.org> <407CD31D.5080001@univ-savoie.fr> <44F959F8-8DEB-11D8-A972-000393DBC266@epfl.ch> <407D0289.5090807@univ-savoie.fr> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <6602876C-8E09-11D8-A972-000393DBC266@epfl.ch> Content-Transfer-Encoding: quoted-printable Cc: caml-list@inria.fr From: =?ISO-8859-1?Q?Daniel_B=FCnzli?= Subject: Re: [Caml-list] Scheduling thread problem kernel 2.6 Date: Wed, 14 Apr 2004 13:46:42 +0200 To: Christophe Raffalli X-Mailer: Apple Mail (2.613) X-Miltered: at nez-perce by Joe's j-chkmail ("http://j-chkmail.ensmp.fr")! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 raffalli:01 callbacks:01 serialize:01 callbacks:01 lablglut:01 implemented:01 37.:99 ecrit:01 kernel:01 christophe:01 bindings:01 bindings:01 caml:01 caml:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk X-Status: X-Keywords: X-UID: 321 =09 Le 14 avr. 04, =E0 11:21, Christophe Raffalli a =E9crit : > You do not need in general to enter a blocking section when calling C.=20= > you only need that if you call some specific Caml function from C (if=20= > I remember well) True, this message [1] confirms it (point 6) and since callbacks are=20 not executed concurrently by glut there is no need to serialize them=20 with enter/leave_block_section(). Apparently [2]=20 enter/leave_blocking_section() are mainly used to allow the execution=20 of signal callbacks during execution of long running C code that=20 doesn't interact with caml code (this means that if I use the lablglut=20= bindings, my signal callbacks will never be executed, so I think it=20 would be better to use enter/leave_blocking_section() in the bindings=20 as depicted in my previous message). Regarding your problem, maybe glutMainLoop() is doing busy waiting. You=20= can try to look into the code [3], glutMainLoop() is implemented in=20 file lib/glut/glut_event.c. However this wouldn't explain the fact that=20= your program was running well in another version of your system. Daniel [1] [2] [3] = ------------------- 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