From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [PATCH] Futures: Avoid creating the worker pool more than once
Date: Thu, 08 Nov 2012 20:11:24 +0100 [thread overview]
Message-ID: <87zk2rc3kz.fsf@gnu.org> (raw)
In-Reply-To: 87a9uu9vpk.fsf@tines.lan
Mark H Weaver <mhw@netris.org> skribis:
> + ;; setting 'create-workers!' to a no-op is an optimization, but it is
> + ;; still possible for '%create-workers!' to be called more than once
> + ;; from different threads. Therefore, to avoid creating %workers more
> + ;; than once (and thus creating too many threads), we check to make
> + ;; sure %workers is empty within the critical section.
Do you have a scenario where this happens?
Ludo’.
next prev parent reply other threads:[~2012-11-08 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 23:07 [PATCH] Futures: Avoid creating the worker pool more than once Mark H Weaver
2012-11-07 13:46 ` Mark H Weaver
2012-11-07 14:14 ` Daniel Hartwig
2012-11-16 23:15 ` Ludovic Courtès
2012-11-30 19:01 ` Mark H Weaver
2012-11-30 20:14 ` Ludovic Courtès
2012-11-08 19:11 ` Ludovic Courtès [this message]
2012-11-10 3:13 ` Mark H Weaver
2012-11-10 13:53 ` Ludovic Courtès
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=87zk2rc3kz.fsf@gnu.org \
--to=ludo@gnu.org \
--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).