From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org, djurfeldt@nada.kth.se
Subject: Re: Thread interface issues (was Re: C level mutices and condition variables)
Date: 22 Nov 2002 22:27:25 +0100 [thread overview]
Message-ID: <877kf5fg76.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m31y5qwfju.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> Given the renewed discussion, could we not have both
>
> - a low level, implementation-dependent scm_t_mutex, with no fairness
> guarantees, that is as native as possible w.r.t. the thread impl
>
> - fair SCM mutexes built on top of scm_t_mutex.
Yep, I think this is the way to go. When I find some time, I'll
revert the deprecation of scm_t_mutex etc and document that API in
addition to the Scheme API. I will make it so that when we use
pthreads, there wont be any overhead whatsoever when using scm_t_mutex
(compared to using pthreads directly).
Mikael, when you want to work on this yourself, that would be great.
Just tell me briefly.
--
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-11-22 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 20:12 C level mutices and condition variables Marius Vollmer
2002-10-26 21:28 ` Neil Jerram
2002-10-26 23:33 ` Marius Vollmer
2002-10-27 7:40 ` Neil Jerram
2002-10-27 12:37 ` Marius Vollmer
2002-11-11 22:05 ` Thread interface issues (was Re: C level mutices and condition variables) Mikael Djurfeldt
2002-11-12 22:37 ` GC & threads (was: Thread interface issues) Han-Wen Nienhuys
2002-11-12 23:09 ` Thread interface issues (was Re: C level mutices and condition variables) Neil Jerram
2002-11-22 21:27 ` Marius Vollmer [this message]
2002-11-23 20:55 ` Thread interface issues Mikael Djurfeldt
2002-11-24 10:27 ` Marius Vollmer
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=877kf5fg76.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=djurfeldt@nada.kth.se \
--cc=guile-devel@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).