summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@nvidia.com>2024-02-03 14:52:38 +0100
committerDonald Sharp <sharpd@nvidia.com>2024-02-05 20:51:55 +0100
commitc1e20869306b5cc8be74ae43fe12a9557a61ae5d (patch)
treed404de3b2391262f157d9e8d059f3aed24709601 /doc
parentMerge pull request #15291 from idryzhov/mgmtd-yang-embed (diff)
downloadfrr-c1e20869306b5cc8be74ae43fe12a9557a61ae5d.tar.xz
frr-c1e20869306b5cc8be74ae43fe12a9557a61ae5d.zip
doc: Add some documentation around a new pthread call
Not necessarily the correct place for this but there is no other place and it needs to be called out and I would rather have some documentation in place. Long term I would like to add a bunch of frr_pthread documentation but at this point in time it's not there. We can re-arrange when that happens. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/developer/rcu.rst9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/developer/rcu.rst b/doc/developer/rcu.rst
index 4fd56587a..2335e8fae 100644
--- a/doc/developer/rcu.rst
+++ b/doc/developer/rcu.rst
@@ -232,6 +232,15 @@ Internals
that case, either all of the library's threads must be registered for RCU,
or the code must instead pass a (non-RCU) copy of the data to the library.
+.. c:function:: int frr_pthread_non_controlled_startup(pthread_t thread, const char *name, const char *os_name)
+
+ If a pthread is started outside the control of normal pthreads in frr
+ then frr_pthread_non_controlled_startup should be called. This will
+ properly setup both the pthread with rcu usage as well as some data
+ structures pertaining to the name of the pthread. This is especially
+ important if the pthread created ends up calling back into FRR and
+ one of the various zlog_XXX functions is called.
+
.. c:function:: void rcu_shutdown(void)
Stop the RCU sweeper thread and make sure all cleanup has finished.