From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: djurfeldt@nada.kth.se
Subject: Re: crypt mutex
Date: Fri, 20 Feb 2004 22:24:37 -0500 [thread overview]
Message-ID: <xy71xopktca.fsf@nada.kth.se> (raw)
In-Reply-To: <87znbdi85m.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 21 Feb 2004 10:32:53 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> While nosing around the crypt function, I wondered if it ought to have
> a mutex, just in case two threads run it concurrently.
We probably need a policy which regulates when to have and when to not
have a mutex.
Personally, I wouldn't like Guile to have everything thread-safe
"under the hood". That would be a terrible waste of resources.
I think it is completely OK to specify that certain resources are not
thread safe, and that if a user writes a threaded program which uses
such resources in parallel, he needs to himself supply necessary
mutexes etc.
So, the policy needs to specify where the border between Guile and
user responsibility goes. In most cases, I would probably draw the
line so that as much as possible of the responsibility is left to the
user with the exceptions that 1. Guile should never segfault due to
misuse in this respect, and, 2. Guile need to have enough thread
safety so that it's reasonably convenient to write parallel programs.
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-21 3:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 0:32 crypt mutex Kevin Ryde
2004-02-21 3:24 ` Mikael Djurfeldt [this message]
2004-02-21 3:26 ` Mikael Djurfeldt
2004-02-23 19:15 ` Marius Vollmer
2004-02-21 21:50 ` Kevin Ryde
2004-02-23 19:16 ` Marius Vollmer
2004-02-23 19:12 ` Marius Vollmer
2004-02-23 19:46 ` Mikael Djurfeldt
2004-02-23 19:55 ` Mikael Djurfeldt
2004-02-24 1:11 ` Andreas Voegele
2004-02-24 1:22 ` Mikael Djurfeldt
2004-03-20 22:39 ` Marius Vollmer
2004-03-20 22:51 ` Kevin Ryde
2004-07-23 23:53 ` Kevin Ryde
2004-02-23 20:01 ` Mikael Djurfeldt
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=xy71xopktca.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
/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).