From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-user@gnu.org
Subject: Re: Threads and asyncs
Date: 03 Sep 2002 20:06:03 +0200 [thread overview]
Message-ID: <87d6rvaqyc.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87it1oglmq.fsf@zagadka.ping.de>
Marius Vollmer <mvo@zagadka.ping.de> writes:
> Also, a thread would wake up when it is blocked and run its asyncs
> anyway.
I'd like to draw your attention to this. What do you think of it?
When a thread blocks to wait for a mutex, say, it will wake up when a
async is marked for it and run that async. Then it will go to sleep
again (unless it has acquired the mutex). Likewise for condition
variables, select and other kind of blocks.
Also, I think we need a single mechanism that can block on multiple
objects. For that, we should probably extend 'select' to also handle
mutixes, condition variables, thread joins, and maybe other things.
I have made asyncs per-thread in my working copy and they work fine.
I have also added 'current-thread' and 'all-threads' functions, which
I think are useful.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-09-03 18:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 20:52 Threads and asyncs Marius Vollmer
2002-09-02 21:24 ` Tom Lord
2002-09-02 21:53 ` Marius Vollmer
[not found] ` <87bs7ggiss.fsf@zagadka.ping.de>
2002-09-02 22:24 ` Tom Lord
2002-09-02 23:51 ` Marius Vollmer
2002-09-02 23:02 ` Rob Browning
2002-09-02 23:24 ` Tom Lord
2002-09-02 23:36 ` Tom Lord
2002-09-02 23:52 ` Lynn Winebarger
2002-09-03 0:57 ` Tom Lord
2002-09-03 1:13 ` Thomas Bushnell, BSG
2002-09-03 1:29 ` Tom Lord
2002-09-03 1:31 ` Tom Lord
2002-09-03 1:00 ` Thomas Bushnell, BSG
2002-09-03 1:28 ` Tom Lord
2002-09-03 1:23 ` RnRS process/history/documentation (was Re: Threads and asyncs) Lynn Winebarger
2002-09-03 1:27 ` Threads and asyncs Rob Browning
2002-09-03 1:45 ` Tom Lord
2002-09-03 1:48 ` Lynn Winebarger
2002-09-04 23:46 ` Lynn Winebarger
2002-09-05 0:20 ` Tom Lord
2002-09-05 1:45 ` Lynn Winebarger
2002-09-05 2:38 ` Tom Lord
2002-09-05 2:30 ` Thomas Bushnell, BSG
2002-09-05 2:43 ` Tom Lord
2002-09-05 2:40 ` Thomas Bushnell, BSG
2002-09-05 3:00 ` Tom Lord
2002-09-05 2:57 ` Thomas Bushnell, BSG
2002-09-05 3:23 ` Tom Lord
2002-09-05 3:14 ` Lynn Winebarger
2002-09-05 4:00 ` Tom Lord
2002-09-05 3:51 ` Thomas Bushnell, BSG
2002-09-05 4:01 ` Tom Lord
2002-09-05 22:03 ` Lynn Winebarger
2002-09-03 1:34 ` Thomas Bushnell, BSG
2002-09-03 18:06 ` Marius Vollmer [this message]
2002-09-04 0:28 ` NIIBE Yutaka
2002-09-04 18:02 ` Marius Vollmer
2002-09-04 22:30 ` NIIBE Yutaka
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d6rvaqyc.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-user@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).