From: "Ondřej Surý via lttng-dev" <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] RCU API usage from call_rcu callbacks?
Date: Wed, 22 Mar 2023 12:08:33 +0100 [thread overview]
Message-ID: <D3F46FB3-2D4B-442D-99A3-F9DEB3918731@sury.org> (raw)
Hi,
the documentation is pretty silent on this, and asking here is probably going to be faster
than me trying to use the source to figure this out.
Is it legal to call_rcu() from within the call_rcu() callback?
What about the other RCU (and CDS) API calls?
How does that interact with create_call_rcu_data()? I have <n> event loops and I am
initializing <n> 1:1 call_rcu helper threads as I need to do some per-thread initialization
as some of the destroy-like functions use random numbers (don't ask).
If it's legal to call_rcu() from call_rcu thread, which thread is going to be used?
Thank you,
Ondrej
--
Ondřej Surý (He/Him)
ondrej@sury.org
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2023-03-22 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 11:08 Ondřej Surý via lttng-dev [this message]
2023-03-22 13:57 ` Mathieu Desnoyers via lttng-dev
2023-03-22 14:45 ` Paul E. McKenney via lttng-dev
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D3F46FB3-2D4B-442D-99A3-F9DEB3918731@sury.org \
--to=lttng-dev@lists.lttng.org \
--cc=ondrej@sury.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