From: Kevin Ryde <user42@zip.com.au>
Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org
Subject: Re: crypt mutex
Date: Sun, 21 Mar 2004 08:51:57 +1000 [thread overview]
Message-ID: <878yhv3zea.fsf@zip.com.au> (raw)
In-Reply-To: <87hdwjnnxq.fsf@zagadka.ping.de> (Marius Vollmer's message of "Sat, 20 Mar 2004 23:39:13 +0100")
Marius Vollmer <mvo@zagadka.de> writes:
>
> Yes, that is what I meant. But, if making a function be reentrant
> takes a mutex then we should not hesitate to use one.
Speaking of mutexes, the reason I haven't checked in what I posted is
that I'm wondering if crypt should have its own private mutex.
A mutex for every function seems a bit wasteful, even if it would give
maximum parallelism. I'm thinking crypt is cpu-only and not often
run, so might as well share a single global mutex.
Incidentally, crypt_r measures significantly slower (about 5x) than
crypt, presumably because it does various initializations, so I'm
thinking not to use that.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-03-20 22:51 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
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 [this message]
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=878yhv3zea.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).