From: Damien Mattei <damien.mattei@gmail.com>
To: guile-user <guile-user@gnu.org>
Subject: fibers,questions about thread id and mutation of vectors
Date: Fri, 6 Jan 2023 11:20:05 +0100 [thread overview]
Message-ID: <CADEOadcJmiNnDe2Vh98aZBFOMufH0oJvbDOPsx=nnGv8hwJ61A@mail.gmail.com> (raw)
Hi,
is fibers having a way to know the thread number the code is running?
i, mean the equivalent of omp_get_thread_num(); in openMP.
Does vector-set! (i read the mutation section of the docand i suppose it is
wrapped/rewritten for fibers) in fibers let many thread access a vector
without time penalty if the index access are differents? (because if index
are different there is no real concurrency)
Regards,
Damien
next reply other threads:[~2023-01-06 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 10:20 Damien Mattei [this message]
2023-01-06 14:12 ` fibers,questions about thread id and mutation of vectors Maxime Devos
2023-01-06 15:06 ` Damien Mattei
2023-01-06 17:06 ` Damien Mattei
2023-01-06 17:06 ` Maxime Devos
2023-01-13 11:10 ` Damien Mattei
2023-01-13 12:23 ` Maxime Devos
2023-01-17 9:42 ` Damien Mattei
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='CADEOadcJmiNnDe2Vh98aZBFOMufH0oJvbDOPsx=nnGv8hwJ61A@mail.gmail.com' \
--to=damien.mattei@gmail.com \
--cc=guile-user@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).