Arm backend: Decrease scratch buffer for Dedicated_Sram #12891
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.
For Dedicated_Sram, both ET_ARM_BAREMETAL_METHOD_ALLOCATOR_POOL and ET_ARM_BAREMETAL_SCRATCH_TEMP_ALLOCATOR_POOL shares the DDR memory area with the parameters of the network.
The DDR is 256MiB, so if we allocate 60MiB + 128MiB for buffers, that only leaves 68Mib for the parameters, severely limiting the size of network we are able to run.
cc @digantdesai @freddan80 @per @zingo @oscarandersson8218