From: John Max Skaller <skaller@ozemail.com.au>
To: caml-list@inria.fr
Subject: Re: [Caml-list] gc question: thread stacks, fibers, etc.
Date: Sun, 13 Oct 2002 02:33:36 +1000 [thread overview]
Message-ID: <3DA84EE0.806@ozemail.com.au> (raw)
In-Reply-To: <4.3.2.7.2.20021004000748.030bd2c0@mail.d6.com>
Chris Hecker wrote:
>
> Fibers/Coroutines/Cooperative-Threads
> In C, you implement them by mallocing a stack and with a little snippet
> of asm, or mucking with the jmpbuf fields. They're pretty trivial to
> get working fairly robustly
.. and fairly useless in most demanding applications due to the
impossibility of dynamically extending/shrinking the stack.
If that isn't a problem .. you might as well just use
real threads ..
Felix solves this problem by using heap allocated stack
frames .. there is a cost in that many procedure calls
must be done indirectly via a driver routine which
maintains the top of stack pointer for each thread.
It also preserves high efficiency by disallowing
blocking I/O (yields) in functional code, which use
the machine stack as usual.
BTW: I consider the technique a case of continuations,
but it is probably more correct to consider it
as a system of resumptions.
--
John Max Skaller, mailto:skaller@ozemail.com.au
snail:10/1 Toxteth Rd, Glebe, NSW 2037, Australia.
voice:61-2-9660-0850
-------------------
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
next prev parent reply other threads:[~2002-10-12 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 10:25 Chris Hecker
2002-10-06 18:13 ` [Caml-list] Coroutines Jerome Vouillon
2002-10-06 19:46 ` Chris Hecker
2002-10-12 15:58 ` John Max Skaller
2002-10-12 16:33 ` John Max Skaller [this message]
2002-10-12 18:54 ` [Caml-list] gc question: thread stacks, fibers, etc Chris Hecker
2002-10-13 8:32 ` Xavier Leroy
2002-10-14 7:18 ` Chris Hecker
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=3DA84EE0.806@ozemail.com.au \
--to=skaller@ozemail.com.au \
--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