[V4.2.3] Improve maximum network buffer allocation size check when Buffer Allocation scheme 1 is used #1265
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
…rs and use it to verify allocation requests when using Buffer Allocation 1
…ocateRAMToBuffers
ActoryOu
approved these changes
Jun 10, 2025
kar-rahul-aws
approved these changes
Jun 10, 2025
tony-josi-aws
force-pushed
the
v4.2.3_test
branch
from
8505467 to
61dda26
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
This PR improves the maximum network buffer allocation size check when Buffer Allocation scheme 1 is used by returning the number of bytes allocated per network buffer by the network interface when the statically allocated buffers are initialized.
Test Steps
Tested on STM32F4
Checklist:
[ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.