Repository navigation
feat: bound CON response storage - #96
Merged
Merged
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
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.
Replace allocating CON response APIs with caller-owned datagram, option, and bounded Block2 storage. Completed results retain their bytes and metadata until caller reuse; capacity failures are correlated by handle and release client state. Remove result deinit/sentinel flags, add local cancellation, and harden blockwise and separate-response handling.
Synchronize DTLS benchmark workers and use common-wall successful-response throughput. Include matched original-library controls, allocator-separated results, and ownership/benchmark documentation. This intentionally breaks the CON API; raw receive and Observe allocator APIs remain explicit.
Verification: 194/194 Debug and ReleaseSafe tests, Debug/ReleaseFast builds, IPv6 DTLS smoke, and 132 final zero-error benchmark comparisons. Single-worker ReleaseFast DTLS improves 2.2–3.4x with DebugAllocator; matched SMP is approximately unchanged. Four-worker variance and negative cells are retained and qualified in docs/CON_BUFFERS.md.