counters: add "counters-disabled"
feature flag
#1658
Merged
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.
The
ringbuf
crate has a"disabled
feature flag, which disables ring buffers, intended for use on memory-constrained targets. Currently, setting the"disabled"
feature flag still enables counters for ring buffers declared using thecounted_ringbuf!
macro, because counters generally require less RAM than full ringbufs. However, on some targets, even counters are too large, especially when a ringbuf's entry type has too many variants (e.g. see this comment from @bcantrill --- thei2c_driver
ringbuf must disable counters in order to fit in Donglet's RAM).Therefore, this commit adds an additional
"counters-disabled"
feature flag to theringbuf
crate, to allow disabling counters as well as ring buffers.