-
-
Notifications
You must be signed in to change notification settings - Fork 82
Cmm threadsafe docs #367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Cmm threadsafe docs #367
Conversation
Thanks! |
@h2zero how does this one look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one comment, thanks!
|
||
When commands are sent to the stack from a different core they can experience delays in execution. | ||
This library detects this and invokes the esp32 IPC to reroute these commands through the correct core but this also increases overhead. | ||
This library is threadsafe. It detects calls from other cores and invokes the esp32 IPC to reroute these commands through the correct core but this also increases overhead. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is no longer relevant, the IPC is no longer used, so just removing this will be best to prevent any confusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@h2zero so we should remove the Nimble thread section entirely:
## Put BLE functions in a task running on the NimBLE stack core
When commands are sent to the stack from a different core they can experience delays in execution.
This library is threadsafe. It detects calls from other cores and invokes the esp32 IPC to reroute these commands through >
Therefore it is highly recommended to create tasks for BLE to run on the same core, the macro `CONFIG_BT_NIMBLE_PINNED_TO_>
<br/>
and then add a
## Threadsafety
This library is threadsafe.
Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@h2zero thoughts on what we might put here? Would like to wrap this one up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that is all that is needed, maybe extend it with attributes can be manipulated freely
or something like that.
e366930
to
4fb4ee9
Compare
No description provided.