doc: Add some documentation around a new pthread call #15287
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
idryzhov
reviewed
Feb 3, 2024
doc/developer/rcu.rst
Outdated
| @@ -60,6 +60,7 @@ RCU is designed for read-heavy workloads where objects are updated relatively | |||
| rarely, but frequently accessed. Do *not* indiscriminately replace locking by | |||
| RCU patterns. | |||
|
|
|||
| 57a63d9009 zebra: eheck sscanf return value | |||
There was a problem hiding this comment.
I suppose this is not needed here.
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 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.