From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Parallel Guile code called from parallel C code
Date: Sun, 21 Aug 2011 11:22:53 +0200 [thread overview]
Message-ID: <877h6715le.fsf@gnu.org> (raw)
In-Reply-To: CADN58OrDNokzo8LXHWTL-A_n6gZasVoZMhfJn16ZJZ0YjwpALw@mail.gmail.com
Hi,
pablo <r@uzy.me> skribis:
> The Guile doc says "Internally, a fixed-size pool of threads is used
> to evaluate futures, (...) the pool contains one thread per available
> CPU core, minus one, to account for the main thread."
>
> Then how does this work in the situation I described? Do the two
> concurrent parallel Guile functions use threads from the same pool or
> is there actually two pool? (ie. does each C threads calling a Guile
> function have an independent Guile environment regarding the possible
> parallelization of the Guile function itself?)
There’s a single thread pool per Guile instance. See ice-9/futures.scm:
there’s a global variable holding a list of threads, basically.
HTH,
Ludo’.
prev parent reply other threads:[~2011-08-21 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 15:49 Parallel Guile code called from parallel C code pablo
2011-08-21 9:22 ` Ludovic Courtès [this message]
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=877h6715le.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).