-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mtk: fix memory allocation problem #8385
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -115,7 +115,7 @@ | |
#define HEAP_RT_COUNT64 32 | ||
#define HEAP_RT_COUNT128 32 | ||
#define HEAP_RT_COUNT256 32 | ||
#define HEAP_RT_COUNT512 4 | ||
#define HEAP_RT_COUNT512 32 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fwiw, Intel has not had to make a change like this since switching RTOS to Zephyr. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. https://github.com/thesofproject/sof/blob/main/src/platform/library/include/platform/lib/memory.h#L97 Btw, 4-->32 too big? do you observe around 15k bytes needed to enlarge? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. After confirming that 15k is only a small portion of the heap buffer, I am uncertain whether there may be other use cases that require a larger buffer size. Therefore, I decided to follow the solution in #7982. |
||
#define HEAP_RT_COUNT1024 4 | ||
#define HEAP_RT_COUNT2048 2 | ||
#define HEAP_RT_COUNT4096 2 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@singalsu @iuliana-prodan did we not recently change this in another place ? I think the newer xtensa compilers are possibly stricter here and hence we are hitting this now.