Skip to content

Using a RT-safe memory allocator #2051

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

Open
christophfroehlich opened this issue Feb 14, 2025 · 2 comments
Open

Using a RT-safe memory allocator #2051

christophfroehlich opened this issue Feb 14, 2025 · 2 comments

Comments

@christophfroehlich
Copy link
Contributor

Question: would using an RT-safe memory allocator not be a more scalable approach?

@gavanderhoorn Do you have some pointers for us? (no pun intended! :D )

Originally posted by @bmagyar in #1801 (comment)

@gavanderhoorn
Copy link

gavanderhoorn commented Feb 18, 2025

On the Implementing a custom memory allocator page there is a (tiny) section about using TLSF.

@yassine-cherni
Copy link

yassine-cherni commented Apr 8, 2025

Hello, i've made this PR , #2169 it need to be improved little bit, we still need some Pointers ;'')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants