From: Christopher Cramer <crayc@pyro.net>
Subject: future thread interface
Date: Tue, 1 Jul 2003 01:32:50 -0500 [thread overview]
Message-ID: <20030701013250.A12964@kiwi.pyrotechnics.com> (raw)
I have a few questions about where Guile is heading wrt to threads.
1. The goal is to be able to pick between different thread
implementations. When is this choice actually supposed to be made: compile
time, link time, during Guile startup, or when? Right now (looking at CVS)
it's compile time, but it looks like the goal is during Guile startup;
It just doesn't seem to be stated anywhere.
2. The prevailing view is apparently that at some point in time
coop thread support will be completely dropped. When is this going
to happen? Personally I would like to keep using coop threads until
pthreads on Linux/glibc gets much more efficient than it is now. I don't
use Guile on any multiprocessor systems, but I expect that eventually
the efficiency problems will be small enough to be outweighed by
the relative simplicity of pthreads.
3. A while ago I was working on a patch to eliminate all the blocking
caused by accept/connect/etc. If I finish it now, can it possibly included
in 1.6.5 (or in 1.6.x at all), or should I target the patch for 1.7?
--
Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
"People said it couldn't be that our soldiers would do such things. Now
you read worse things in the mainstream media and people don't care. We
used to say that if only people know about it, it would stop. Now they
know about it, and it hasn't stopped." - Adam Keller
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-07-01 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 6:32 Christopher Cramer [this message]
2003-07-01 10:27 ` future thread interface Marius Vollmer
2003-07-01 18:57 ` Christopher Cramer
2003-07-05 12:05 ` Mikael Djurfeldt
2003-07-27 16:51 ` 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=20030701013250.A12964@kiwi.pyrotechnics.com \
--to=crayc@pyro.net \
/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).