From: Marius Vollmer <mvo@zagadka.de>
Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org
Subject: Re: SCM_DEFER_INTS versus error
Date: Tue, 07 Oct 2003 19:54:10 +0200 [thread overview]
Message-ID: <87ad8d7x31.fsf@zagadka.ping.de> (raw)
In-Reply-To: <xy7u174b9o0.fsf@nada.kth.se> (Mikael Djurfeldt's message of "Mon, 22 Sep 2003 21:01:03 -0400")
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
> Well, that was the situation with your COPT threads.
Ooops, yes, I could have known this...
> The current PTHREADS thread support of HEAD actually allow true
> concurrent access to Guile data structures. The "kernel lock" is
> only used to force single-threaded GC. The rest of the time,
> threads run in parallel.
Impressive. I _am_ a bit nervous about programming in such an
environmnt, I have to say, but I think I just have to get used to it.
For Scheme code, this is no change compared to the copt model since
Scheme code had to expect preemption anyway.
--
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:[~2003-10-07 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 1:37 SCM_DEFER_INTS versus error Kevin Ryde
2003-09-17 22:58 ` Marius Vollmer
2003-09-19 20:34 ` Tom Lord
2003-09-22 18:01 ` Marius Vollmer
2003-09-20 23:44 ` Kevin Ryde
2003-09-22 18:10 ` Marius Vollmer
2003-09-23 1:01 ` Mikael Djurfeldt
2003-10-07 17:54 ` Marius Vollmer [this message]
2003-12-06 21:15 ` Kevin Ryde
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=87ad8d7x31.fsf@zagadka.ping.de \
--to=mvo@zagadka.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).