Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] Native threads under Debian 3.0r0
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2002-09-04 (15:12)
From: Berke Durak <berke@a...>
Subject: Re: [Caml-list] Native threads under Debian 3.0r0
On Wed, Sep 04, 2002 at 03:01:51PM +0200, Markus Mottl wrote:
> On Wed, 04 Sep 2002, Jacques Garrigue wrote:
> > So the answer is: a native code thread should be allocating some data,
> > otherwise it cannot be interrupted. The problem does not exist for
> > bytecode.
> The main consideration is obviously native code performance. OTOH, some
> people might want to guarantee that their threads never get stuck. I
> don't know what solution would be useful for them. Maybe some runtime
> or command-line switch that trades efficiency against such scheduling
> problems.

Sorry about my ignorance, but aren't threads scheduled by the kernel
when using libpthread ? (That would make sense, since I get extra
processes when I create extra threads). I mean, aren't the threads
automatically preempted ?

If not, couldn't it be possible to preempt them automatically using
the interval timer ?
To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: