From: ludo@gnu.org (Ludovic Courtès)
To: David Pirotte <david@altosw.be>
Cc: 12789-done@debbugs.gnu.org
Subject: bug#12789: threads - proc-map - multicore issue
Date: Sat, 03 Nov 2012 22:06:50 +0100 [thread overview]
Message-ID: <87objegzv9.fsf@gnu.org> (raw)
In-Reply-To: <20121102220727.31148af5@capac> (David Pirotte's message of "Fri, 2 Nov 2012 22:07:27 -0200")
Hi David,
David Pirotte <david@altosw.be> skribis:
> in the following example, the cores, 4 in my case, are used for a couple of seconds,
> then at some point only one core is used:
>
> guile -c '(begin (use-modules (ice-9 threads)) (par-map 1+ (iota 400000)))'
I fixed it just after we discussed it on IRC, in commit 134c95f of
stable-2.0.
Thanks again for the report!
Ludo’.
prev parent reply other threads:[~2012-11-03 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-03 0:07 bug#12789: threads - proc-map - multicore issue David Pirotte
2012-11-03 21:06 ` 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=87objegzv9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=12789-done@debbugs.gnu.org \
--cc=david@altosw.be \
/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).