pkg/openthread: migrate to event loop#15038
Merged
aabadie merged 1 commit intoRIOT-OS:masterfrom Sep 29, 2020
Merged
Conversation
a2d7f1e to
3cd82f9
Compare
aabadie
reviewed
Sep 22, 2020
Contributor
aabadie
left a comment
There was a problem hiding this comment.
I find the new event based approach much nicer. It also allows to get rid of the custom messages defines.
Code-wise things looks good. Just some minor nits but besides this, this PR should be ready to go.
3cd82f9 to
34b3f55
Compare
Member
Author
|
@aabadie thanks for the review! I amended directly |
1 task
This file contains hidden or 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
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.
Contribution description
This PR migrates OpenThread the OpenThread implementation from message queues to event threads.
Besides saving ROM and RAM, this:
a) Opens the door for using an external event queue e.g when using GNRC on top of OpenThread (TBD :)
b) Makes OpenThread more responsive: it seems the message queue was getting full from time to time. Now everything seems to run smoothly.
Testing procedure
This one is easier to test with IoT-LAB. Book a list of nodes (I'm booking the full row of nodes in Grenoble). Use
examples/openthread:a) Check that after some seconds there's only one leader. All the others should be either router or child. Use the
statecommand.Output
b) Try pinging between nodes. Here's a multihop example:
Issues/PRs references
None so far