Issue #25: Improve ULog to better suit current requirements#42
Closed
hasslesstech wants to merge 3 commits intomainfrom
Closed
Issue #25: Improve ULog to better suit current requirements#42hasslesstech wants to merge 3 commits intomainfrom
hasslesstech wants to merge 3 commits intomainfrom
Conversation
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
1 participant
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.
This set of changes increases the size of the message queue to handle the initial spike of messages and significantly reduces the stack memory cost of calling
ULOG_*macros by allocating a static message buffer which is then shared by all tasks. Single shared buffer eliminates the need to allocate large stack frames for individual tasks reducing not only the overall memory consumption, but also the probability of underestimating stack sizes.Shared message buffer is protected by a mutex so that only one execution context can access it at any given time.
All changes are backwards-compatible and follow the existing API.