From: Goswin von Brederlow <goswin-v-b@web.de>
To: Romain Beauxis <toots@rastageeks.org>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Smart ways to implement worker threads
Date: Fri, 16 Jul 2010 15:05:10 +0200 [thread overview]
Message-ID: <871vb3bmrd.fsf@frosties.localdomain> (raw)
In-Reply-To: <201007152319.10974.toots@rastageeks.org> (Romain Beauxis's message of "Thu, 15 Jul 2010 23:19:10 -0500")
Romain Beauxis <toots@rastageeks.org> writes:
> Le jeudi 15 juillet 2010 22:52:53, Goswin von Brederlow a écrit :
>> The main task will only process priority 0 events and bounce between
>> main_task and with_checksum while the worker threads process priority 1
>> events and do_checksum.
>>
>> Correct?
>
> I think it should be like this:
>
> let do_checksum buf _ =
> let sum = ...
> in
> reply_request ();
> []
>
> let main () =
> let scheduler = Duppy.create ()
> in
> for i = 1 to num_cores do
> Thread.create (Duppy.queue ~priorities=(fun x -> x = 1) scheduler "worker") ();
> done;
> while (* New checksum need to be computed *) do
> Duppy.Task.add scheduler
> { priority = 1; events = [`Timeout 0.]; handler = fun _ -> do_checksum buf; }
> done
>
> It seems in your case you do not need finer-grained priority and all the
> workers live at the same priority level..
>
> Now, the main thread does not need to be a task..
But then how does the main thread notice when a checksum is finished
computing? The information has to flow both ways.
MfG
Goswin
next prev parent reply other threads:[~2010-07-16 13:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 16:09 Goswin von Brederlow
2010-07-15 15:58 ` [Caml-list] " Rich Neswold
2010-07-15 16:19 ` David McClain
2010-07-15 17:16 ` Ashish Agarwal
2010-07-15 18:24 ` Goswin von Brederlow
2010-07-15 18:37 ` David McClain
2010-07-15 18:40 ` David McClain
2010-07-15 19:56 ` Rich Neswold
2010-07-16 4:02 ` Goswin von Brederlow
2010-07-16 4:23 ` Rich Neswold
2010-07-16 13:02 ` Goswin von Brederlow
2010-07-16 14:40 ` Dawid Toton
2010-07-16 16:18 ` [Caml-list] " Rich Neswold
2010-07-17 17:53 ` Eray Ozkural
2010-07-20 4:54 ` Satoshi Ogasawara
2010-07-17 18:34 ` Eray Ozkural
2010-07-17 19:35 ` Goswin von Brederlow
2010-07-17 22:00 ` Eray Ozkural
2010-07-15 16:32 ` Romain Beauxis
2010-07-15 17:46 ` Goswin von Brederlow
2010-07-15 18:44 ` Romain Beauxis
2010-07-16 3:52 ` Goswin von Brederlow
2010-07-16 4:19 ` Romain Beauxis
2010-07-16 13:05 ` Goswin von Brederlow [this message]
2010-07-16 13:20 ` Romain Beauxis
2010-07-17 9:07 ` Goswin von Brederlow
2010-07-17 13:51 ` Romain Beauxis
2010-07-17 14:08 ` Goswin von Brederlow
2010-07-17 9:52 ` Goswin von Brederlow
2010-07-17 14:20 ` Romain Beauxis
2010-07-17 15:52 ` Goswin von Brederlow
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=871vb3bmrd.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=caml-list@yquem.inria.fr \
--cc=toots@rastageeks.org \
/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